On 6/28/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > > On Jun 28, 2006, at 11:47 AM, Arnar Birgisson wrote: > > > Right now, TG fires up a thread that updates the visit tracking stuff. > > > > Would it be possible to do something similar for Comet stuff? The idea > > would be that at startup, TG fires up a thread that runs a twised > > reactor. That reactor would listen on a different port than CP for > > "Comet" requests. > > This is an interesting idea, but Twisted is pretty heavyweight, and as > Karl said, there are really a lot of cases that could be handled by > polling rather than traditional "Comet" long-lived requests. > > That being said, if you wanted to implement this, it would be possible > to do using the standard library's asyncore module, plus a little hunk > of code from medusa that allows you to wake up the asyncore loop from > another thread. This would be significantly more lightweight than the > alternative. > > If you need any pointers on how to do this, just let me know.
I will most likely have a look at this soon. I have an upcoming project that includes a sort of BLF (busy-lamp-field) for an Asterisk PBX which would include phone extension status, employee presence and possibly some IM features. I'd like to test Comet instead of polling for updates. Are you talking about using asyncore (which I don't know yet, will read up on it after this email :o) and this code from medusa instead of Twisted, or as a complement? Anyways - any pointers would be well appreciated. :o) Arnar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
