Em Wednesday 05 March 2008 03:49:32 [EMAIL PROTECTED] escreveu: > 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
It is not a matter of work. It is a matter of allocated and unused resources. Database connections, caches, sockets, etc. > 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? And how would that save resources? > By the way, my app is a web chap app that needs to update the > conversation every 1-2 seconds. I'd poll every 2 seconds. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
