On 3/11/07, johnny <[EMAIL PROTECTED]> wrote: > I have an online seminar booking application. What I want to know is, > if 100 people are currently > viewing a room that holds max 200 people, and one person out of 100 > books the seat in the room, how do > I refresh all the 100 pages so that they all have an updated version?
In general, you don't -- this is a limitation of HTTP, because once you send out the response, you've sent out the response. You don't get to send any more data until a new client request comes in. Using a meta refresh is somewhat hackish, but would force a periodic reload for anyone who's just sitting there looking at the page. Similarly, firing off an occasional XMLHttpRequest to fetch updated data will work, and is a bit cleaner. There's also Comet, which is a method coming out of the folks behind the Dojo JavaScript toolkit, and which is based on servers keeping long-lived HTTP connections open so they can keep sending data down the wire, but unfortunately the load of supporting even a few clients in that fashion can quickly murder your server. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
