Menu
Now a days real time updates are common in most popular sites which have heavy usages.
I'm wondering how do these "real time updates" work? I'm just looking for a general bird's view perspective. I suspect that the JS can't be calling the server every X seconds for an update and then appending that to the <ul>. Is a notification sent from the server went to pull more content?
Would be great if there is a simple how to article that explains this with a demo?
884
adjective [ADJECTIVE noun] Real-time processing is a type of computer programming or data processing in which the information received is processed by the computer almost immediately.
You can use Redis as a buffer, and create a separated worker to save in bulk the data from the buffer to your database. You can build all the components in node. js, take into account the language mix in the example above is to show Dockers capability. Save this answer.
Stack Overflow is using Web Sockets for real time updates. If you take a look in the source code (2012 source code), you would see:
StackExchange.ready(function () {
StackExchange.realtime.init('ws://sockets.ny.stackexchange.com');
StackExchange.realtime.subscribeToInboxNotifications();
StackExchange.realtime.subscribeToReputationNotifications('1');
});
But note that some Opera versions do not support WebSocket. (not until Opera 10.70)
However Facebook does not seem to be using Web Sockets, and I think they are just using simple XHR with a technique called long polling, which the server holds on to the connection until there is new information, and then respond to the request. If you open up the developer tools you can see that there is always one request which has a status of pending.
It is indeed, sending a request every ~60 seconds.
138
It seems that Twitter also uses simple XHR (1 minute intervals) for their "real time updates".
22
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
