Near-realtime is fine. You can use an xmlhttp connection to wait for information to be available from the server side, and info from the client side is easily sent. It's not really a turbogears problem as much as a javascript one. The rest is just support (ie, JSON which Turbogears supports).
It's more than quick enough for snappy information, the thing to beware of is the load, ie if you're trying to send a full stockmarket feed then you have to be very very careful about your message design. JSON is a bit too buky for that kind of thing unless they have a very fast link - you want a custom client instead so you can be clever. On Feb 6, 11:43 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I'm wondering about the potential of running what I'm calling services > (think this is the right term) from something like turbogears on a > users machine. Basically, is it realistic to think that a user could > go to a website and have near real time information transactions? I > know that alot of this is based on the connection speed, but assuming > that speed wasn't a factor, could something like turbogears be used > for lets say, streaming content from the client back to the server? My > guess is that the limiting factors would be 1) imagination and skill, > 2) Python's limits, and 3) connection speed (maybe not in that order) > > Thanks for any feedback. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
