On Mar 4, 7:52 pm, Jorge Godoy <[EMAIL PROTECTED]> wrote:
> > More resources than what? polling? I thought Comet was *more*
> > efficient than polling.
>
> Why? You have to keep a connection open to be notified of changes. Polling
> you open and close connections at specific intervals (e.g. every 10 seconds,
> every 1 minute, etc.).
How much work is it to "keep a connection open"?? I agree you'll have
more threads sitting around but they won't be doing any work when
there is nothing for server to push to client. Actually, I don't
recommend multithreaded for Comet apps. If I'm not mistaken, the
ideal would be to have an event driven server so that you wouldn't
need a thread for each long polling client. Wouldn't *that* be best?
e.g. something with Twisted or Orbited (http://www.orbited.org/)
By the way, my app is a web chap app that needs to update the
conversation every 1-2 seconds.
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
