Hi Ben, what kind of latency and scale requirements does your chat box have? And how will it be deployed (shared or dedicated)? Beware that two-way communication over HTTP can add a significant load on the server.
Polling is currently the only *sane* method to do two-way communication with turbogears. Thus if you are expecting allot of (idle) users, turbogears might not be the best server side option. Implementing the client side of a bare-bones chat room wouldn't be to difficult with mochikit. It would involve polling some server side method that returns new messages since a given timestamp. A little DOM swapping will be needed to present the new messages. You would off course also need some method to post new messages. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
