Getting back to the original question, if the refreshes need to happen at fixed (and not too frequent) intervals (rather than at indeterminate times, whenever the data happen to be ready), it may be simpler to just use short-polling -- see https://groups.google.com/d/topic/web2py/xJjTeowYk0U/discussion. Anthony
On Monday, June 6, 2011 8:57:41 PM UTC-4, Anthony wrote: > On Monday, June 6, 2011 7:47:48 PM UTC-4, David J wrote: >> >> Seeing that comet is not widely supportted I was wondering if there was an >> ajax poll example? >> > I think there's some terminology confusion. "comet" *is* widely supported, > as it involves long-held HTTP requests via streaming or Ajax long-polling > (see http://en.wikipedia.org/wiki/Comet_(programming)). Technically, > comet_messaging.py isn't really "comet", but instead uses the newer > WebSockets protocol (see http://en.wikipedia.org/wiki/WebSockets), which > is not yet widely supported by browsers. > > Here's a three-part blog post explaining how to adapt comet_messaging.py to > enable bi-directional messaging and to work with true comet techniques > (e.g., long-polling) via Socket.IO (that's actually covered in part 3): > http://greg.thehellings.com/2011/04/web2py-websockets-and-socket-io-part-i-basic-display/ > > Anthony >
