On 6/28/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > 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 looked around in medusa but didn't see (or reckognize) what you are talking about. Could you point it out to me? :o) Also, do I have the right picture in my head: The Comet-handling-thread idle-loop while there were no clients connected. Once a client (the hidden iframe) connects - it starts the asyncore loop, which pulls messages off a queue and sends them to the client. I'm a bit new to this comet stuff - would I assign each client an ID and tag the messages for them specifically (perhaps some messages could be tagged for multple or "all connected" clients) with that ID? What if the queue contains a message with a client-id that's not connected? Discard the message? Or wait for the client to connect? How did the OP (Bran Vandoren) picture this? 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 -~----------~----~----~----~------~----~------~--~---
