ajax would require to poll every x amount of seconds, comet is one request with pushing capabilities from the server
On Thu, Jul 23, 2009 at 6:33 PM, <[email protected]> wrote: > > > > If it's a webpage, why not just use ajax? JQuery's ajax functions should > make this simple to implement regardless of application framework. > > Phil > > > On Thu, 23 Jul 2009, Brian O'Connor wrote: > > > long polling is when a client requests information (like updates, or in a > > chat room), and the server checks to see if there is new ifnroamtion for > the > > client. if there is, it returns it, if there isn't, it sleeps until > there > > is (keeping the process/thread open). what this achieves is as soon as > > there is new information avaiable, it is immediately pushed to the > client. > > > > It effectively allows a server-push rather than a client-pull > > > > http://en.wikipedia.org/wiki/Comet_(programming)<http://en.wikipedia.org/wiki/Comet_%28programming%29> > > > > > > > > On Thu, Jul 23, 2009 at 6:19 PM, Mike Orr <[email protected]> wrote: > > > >> > >> On Wed, Jul 22, 2009 at 6:09 AM, Brian O'Connor<[email protected]> > >> wrote: > >>> Hello all, > >>> > >>> I've been using pylons for a little while now (actually just developed > a > >>> major university's newspaper web site in it), and am considering it for > >> my > >>> next project. > >>> > >>> This project entails using long-polling extensively and am curious as > to > >> how > >>> pylons holds up to that. > >> > >> What does long polling mean? Is that like where you're returning a > >> large binary file that is created from several external web requests > >> (so it may take a long time to build)? My colleague is encountering > >> this situation, and is currently returning a binary file the normal > >> way (forcing the client to wait or timeout if it takes a long time). > >> We have considered using an asynchronous protocol, where it would > >> return a link to a URL that will be active when the file is ready for > >> download (or 503 Service Unavailable if not ready yet). Or perhaps > >> automatically switch to asynchronous if we think the file will take > >> long to build. > >> > >> Or does long polling mean the client frequently polls the server to > >> see if something has changed? If so, how is that different from > >> normal Pylons usage? > >> > >> Or is it when the server keeps pushing out document parts to the same > >> request as the situation changes? If so, the limitation would be the > >> number of clients that can be accommodated? > >> > >> -- > >> Mike Orr <[email protected]> > >> > >>> > >> > > > > > > > > > > -- Brian O'Connor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
