I\'m building an Objective-C app that has both a server and a client. The client can send updates to the server, and the server needs to be able to send updates to each conn
I don't know how you plan to design you system, but usually a server cannot connect to a client; the client must initiate the communication. With a low limit of 50 clients, you may not be looking at a web-server/client-like implementation...
That said, there are basically two ways to handle client server communication: 1. The client polls the server periodically to get updates 2. The client keeps a connection open to the server and the the server responds with a well known (as in both sides understand it) protocol.