> I want a flow of information, so artificially constructing > the flow as a series of requests sounds do-able but more sensible > would be a single "give me a flow of info" request and a server > construct that can keep open a tcp socket that provides messages until > I'm ready to terminate. Hence my question.
Hi Ross, Like others have said, HTTP is a stateless protocol. There are limited ways to dodge this (cookies, etc.), but the stateless nature is very much by design and should be embraced rather than dodged. In this case, a polling JavaScript interval making XMLHttpRequests is probably the most elegant way to do it. If you are really sold on a "true flow" of data, I would suggest using a small Java app to open a persistant socket with a server. We do this at the company I work for to proxy data between client and server in real time. However, this introduces many other issues (some mentioned above), like opening ports in firewalls, reestablishing lapsed connections, etc. Not to mention, you now have to write a server. Cheers, Ross --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
