In wikipedia it is referred that Remote Socket Address is the Client Socket Address but i doubt that [closed]
Closed 9 years ago.
In wikipedia it is referred that Remote Socket Address is the Client Socket Address but i doubt that [closed]
Closed 9 years ago.
In wikipedia it is referred that Remote Socket Address is the Client Socket Address but i doubt that [closed]
Closed 9 years ago.
“Middle ground” architecture for client-server iOS apps?
I see two obvious approaches to the architecture for an iOS app which needs to talk to a server to do its job.
What is a good design pattern to implement REST services on mobile?
It is easy to implement calls to API endpoints, then to parse JSON and handle the data – but what is a good design pattern for this?
What is a good design pattern to implement REST services on mobile?
It is easy to implement calls to API endpoints, then to parse JSON and handle the data – but what is a good design pattern for this?
What is a good design pattern to implement REST services on mobile?
It is easy to implement calls to API endpoints, then to parse JSON and handle the data – but what is a good design pattern for this?
What is a good design pattern to implement REST services on mobile?
It is easy to implement calls to API endpoints, then to parse JSON and handle the data – but what is a good design pattern for this?
What is a good design pattern to implement REST services on mobile?
It is easy to implement calls to API endpoints, then to parse JSON and handle the data – but what is a good design pattern for this?
How to handle a large amount of authenticated clients
I currently have made a multithreaded server in c++ for windows, where each connected client gets a thread to themselves which stays running until the client’s socket is closed.
When a client connects, they can run commands (fetch motd, get current version of the client) or can login to get access to other commands (fetch user information, download files, etc).