what about a javascript timer that makes a JSON call to check for updates every x minutes? i suspect that the database can be designed in such a way that the query could be quite quick. then you don't need queues and background processes.
just a thought... cfh On Oct 26, 9:23 pm, Tom Campbell <[email protected]> wrote: > I'm writing a scheduling system in web2py. It can be used by multiple > users in multiple locations. If one user adds an appointment, I'd like > other users to see it within 10 seconds or so. What is the preferred > mechanism for this? My poorly educated guess is: > > 1. An updater runs as a single background process as in section 4.19, > checking the database for new or changed appointments at all locations > and enqueues them > 2. Each client schedule running in browser runs a cron job to check > the queue for matching appointments > 3. If any appointments in the queue satisfy the search criteria (i.e. > appointments at that location), the calendar gets redrawn > > Any feedback would be greatly appreciated.
