> > While implementing the polling mechanism for a little progress bar > widget I started to wonder how one would implement the *push* method > using TG. Polling is just fine for my widget yet I can think of widgets > where the push method would be more suitable (eg. a multiuser-editor > widget). > > Instead of bombarding the server with a continues stream of HTTP > requests, the clients would make a single request to the server which > it puts on hold till some update or time-out signal. AFAIK this isn't > currently really feasible with cherrypy because it allocates a thread > per request. Since turbogears makes AJAX so easy it would be nice if we > had some way to shelf a request till further notice. Any thoughts on > this? > > ps. widgets are *really* cool! > > some refs: > http://tinyurl.com/pos5g > http://tinyurl.com/ba88o
That sounds like an abuse of HTTP and a hammer to kill a fly. I could see the benefit in some cases but to be honest I wonder sometimes if people are not pushing HTTP a bit too far. To me it would be much better if Javascript could provide a way to use other protocols than just plain HTTP via XmlHttpRequest so that app dev could create a web frontend and a real application server aside with the proper underlying protocol. HTTP was not meant to do what you suggest. - Sylvain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
