3 ms·
If I understand well, the client browser polls the server, via JS timers. There is no practical, scalable way for the server to update the client browser, so t
by ovi256 17y ago
If I understand well, the client browser polls the server, via JS timers. There is no practical, scalable way for the server to update the client browser, so the client has to poll this way. Their code just answers these polls.
Of course, performance wise, this sucks badly, because most of the time polling returns no results.
- axod 17y ago>> "There is no practical, scalable way for the server to update the client browser, so the client has to poll this way." If you say so :/
- lbrandy 17y agohttp://en.wikipedia.org/wiki/Comet_(programming) http://en.wikipedia.org/wiki/Comet_(programming)
- simonw 17y agoThere are a number of practical, scalable (albeit tricky to set up) ways of pushing events from the server to the browser, gathered under the umbrella term Comet. Google have been using Comet for chat within Gmail since around 2005.
- a-priori 17y agoFacebook also uses it, with an Erlang backend, for Facebook Chat.