On 2/7/07, Jorge Vargas <[EMAIL PROTECTED]> wrote:
>
>
> On 2/5/07, [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)
> >
> As others said the problem here is more with javascript. Now if you
> really need this kind of thing maybe a webpage is not the best thing,
> remember http was designed to be stateless, and sessionless, and of
> course it depends on how much resources you have, since having 100
> clients pinging your server will need more resources then an
> alternative more network oriented implementation like twisted or other
> socket based RPC. Now of course this brings in a lot of complications
> like managing the client software but this may be necesary in order to
> make it work.


If you start running into threading issues you may want to try this:
http://mail.python.org/pipermail/python-list/2004-November/290722.html
If you could put those connections into a map you might be able to pass em
off async. No idea if this would work.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to