3 ms·
Why don't you use long polling rather than sending a request a second? You could even incorporate the timer into a single request. do { sleep(1);
by toolate 16y ago
Why don't you use long polling rather than sending a request a second?
You could even incorporate the timer into a single request.
do {
sleep(1);
$seconds_remaining = fetch_auction_time_from_memcache();
echo "<script>updateActionTime($seconds_remaining);</script>";
flush();
} while ($seconds_remaining > 0);
- BuckToBid 16y agoThis is interesting. Would this work if I was on the site for say an hour? Or is there some limit to the amount of time you can send data like this? I have never tried anything like this. What is the overhead like?
- gcr 16y agoNot hard. The client could notice if the connection dies (JQuery has AJAX failure callbacks, for example) and then attempt to reconnect; that's the important thing.
- toolate 16y agoI've only used it on smaller projects. Facebook use it on their frontpage for progressive loading (check the source for `<script>big_pipe.onPageletArrive(..);</script>`). Longer running connections are a little more problematic, but some client side code should be able to handle the connection being closed. You just need to make sure your web server can handle the number of connections your are expecting. Apache is particularly bad for this. Something like nginx should perform better.
- wanderr 16y agoI was going to suggest long polling as well. Seems to make way more sense than normal polling for this application.