You might want to check out SocketIO (<meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://socket.io/">http://socket.io/</a>)<br><br><div class="gmail_quote">On Fri, May 20, 2011 at 10:14 AM, Michael <span dir="ltr"><<a href="mailto:mdm@yachtpc.com">mdm@yachtpc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Greetings Mappers!<br>
<br>
I've built a trans-pacific charting application intended to be used for near real-time sailboat tracking.<br>
<br>
I want to update positions without users having to press "refresh." While a loop fetching data and updating works for that purpose, we expect, from prior experience, around 90k viewers a day during the actual race (July 2012). Data will consist of around 70 new points, plus some social networking links, per hour.<br>
<br>
It seems that the "long polling" method or, worse, looped queries, can lead to server overload. Web searches keep leading me to Comet and Ape, but it seems that nobody has done any work on these since 2009.<br>
<br>
Can someone in the community enlighten me on what the best thinking is for updating the data on the clients efficiently? Has the field been taken over by mixed commercial enterprises like Lightstreamer? I'd sure like to stay 100% open source.<br>
<br>
Michael<br>
<br>
p.s: Simulation at <a href="http://pacificcup.org/OpenLayers/trackup.php" target="_blank">http://pacificcup.org/OpenLayers/trackup.php</a><br>
A server is set to trickle data out every minute or so. You'll need to pick the boat from the menu at the left.<br>
<br>
m<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.osgeo.org" target="_blank">Users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/openlayers-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-users</a><br>
</blockquote></div><br>