Solved the issue, it turns out it was a bug introduced in socket.io 0.9.5. If you have this issue just update BOTH your server and client-side code to socket.io > 0.9.9 and set the socket.io client-side options sync disconnect on unload to true and you’re all set. Options are set this way: var socket = … Read more
Yeah, the Comet-like techniques usually blowing up the brain in the beginning — just making you think in a different way. And another problem is there are not that much resources available for PHP, cuz everyone’s doing their Comet in node.js, Python, Java, etc. I’ll try to answer your questions, hope it would shed some … Read more
Just for the sake of argument. Both are http request (xhr), and its at least partially untrue it uses more server resources (depends totally on technology, will explain later). Short polling. Lot of request that are processed as they come on server. Creates a lot of traffic (uses resources, but frees them as soon as … Read more
Yes, this behavior is due to Chrome locking the cache and waiting to see the result of one request before requesting the same resource again. The answer is to find a way to make the requests unique. I added a random number to the query string, and everything is working now. For future reference, this … Read more
This is quite straightforward when outputting text or HTML. Below is an example. (You’ll run into issues if trying to output JSON however, which I’ll tackle further down.) PHP FILE header(‘Content-type: text/html; charset=utf-8’); function output($val) { echo $val; flush(); ob_flush(); usleep(500000); } output(‘Begin… (counting to 10)’); for( $i = 0 ; $i < 10 ; … Read more
In the examples below the client is the browser and the server is the webserver hosting the website. Before you can understand these technologies, you have to understand classic HTTP web traffic first. Regular HTTP: A client requests a webpage from a server. The server calculates the response The server sends the response to the … Read more