Originally posted by Chandra Bhatt:
What if this treats your <HEAD> as coconut? Beware balds!!!
Originally posted by Eric Pascarello:
I think setTimeout would be your friend. When the response comes back, you use setTimeout and make it do another call to the server.
I do not recommend using setInterval in this case.
Eric
Originally posted by Ulf Dittmer:
What exactly do you mean by "report display in the front-end"?
Originally posted by Ulf Dittmer:
The app/web server wouldn't have to poll the DB every time one of the clients asked for updates - it could itself check in with the DB periodically, and prefetch the required data if there was a change. Thus the DB load wouldn't rise if there were more and more clients.
Originally posted by Ulf Dittmer:
Most Databases have a concept of triggers that can be fired automatically if certain events (like a table change) occurs, but I would shy away from using that to reach outside of the DB. That would be a twisted design.