Menu
So I created an app where the app connects to the server and tells it to do something. However the server takes a lot of time to do that thing (like an hour or so). So it doesn't make sense to connect the client to the server for that long. I want that the server must create a connection to the client to inform that he is ready to deliver the end result. Then after connection, he sends the data to the client.
I am thinking two ideas here:
I can create a server on the client side also, and client can listen for server to connect. However my clients are usually some desktop apps or mobile apps with limited resources and some of them also are behind a firewall/NAT. So even if they have a server running, I am not sure that my main server will be able to connect to them.
The client can keep checking periodically whether the results are prepared or not. This way the client does not have to maintain any server or anything. It will be the plain old client server architecture. But this costs me a lot of un-necessary traffic, as the result may be available within few minutes to few hours. A client constantly pining the server does not seems too good to me.
I first of all have no idea where to start or google this stuff. I know such a thing exists because I see all the time where servers such as "Skype" informs my desktop app that I have a new friend request, or gmail notification system where Google shows a message on my desktop when new mail is received.
Most google searches are yielding the same stuff where the client connects to the server. But the case is opposite here.
If this question is not upto standard, a few references would also be great, and I will delete this post. There's a great chance that I am just not thinking something and being stupid. Please help. Thanks.
678
RFC 959, Section 3.2: The server, upon receiving the transfer request, will initiate the data connection to the [client] port.
The connection between the server and the client is defined with a network name. The server listens to the network using certain protocols and server names or port numbers. Clients must use a matching connect string when connecting to the server.
To use python socket connection, we need to import socket module. Then, sequentially we need to perform some task to establish connection between server and client. We can obtain host address by using socket. gethostname() function.
The server creates a socket and binds a name to the socket, then displays the port number. The program calls listen(3SOCKET) to mark the socket as ready to accept connection requests and to initialize a queue for the requests.
So after I researched a lot of related articles, here is what I have come up with.
These links describe what is called a "server push" which basically pushes data to the client from server. There are a variety of methods discussed here. My point #2 was actually very near to the solution, and the term for point #2 is called long polling.
But methods discussed in both of these articles are about pushing the data back to the web browser. In some cases, the solution can be extended to server push in mobile clients, but I am still reading on them, so can't comment much.
However, for server to app push, which is kind of what my requirement was, two things really stood up:
I have currently decided to go with Amazon SNS and will also keep learning Redis side by side, just for future use.
Need server push? Forget everything else and use Redis + Socket-IO + Node-JS. How did I not know about Websockets. Its the next best thing.
In my app, I just send any messages to Redis that I want to be pushed to clients. Redis publishes those messages. Socket.IO is listening on the channels using psubscribe to listen on patterns rather than one channel. Category of user is defined by the channel name.
Once socket.io (written in node.js) hears about the message, it simply emit those messages to the client. Clients inturn are listening to socket.io on a specific port. Socket.io supports rooms like channel in redis.
For live examples just google real time chat with socket.io and node.js.
I will also write some examples if anybody requests me to. Its real easy.
176
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
