Im not really sure, It sounds like a lot of work for a certain type of result.
Is it a result set your refreshing? it sounds like you would be much better using something like AJAX, which im not really fond of but in this situation is probably good.
Instead of triggering from the database you could periodically contact your server to check if what ever it is thats supposed to have happened has happened, and then just use client side script to refresh the page.
Does it have to have a response time better than a minute or something like that? Checking every 10-20 minutes if the action has happened would be fairly easy to do with an ajax framework.
I think your going to have trouble actually sending a response to the client if you already have sent a response... http is a stateless protocol, im not even sure of where to start on that. A problem like yours is probably where all this AJAX stuff started.
Oh, and on a side note the Google Web Toolkit has a framework for running client side applications that do asychronous loading of pages, might be worth having a look at it.
good advice Waylander...:-)
However IMHO..Using a hidden frame will do exactly that what "AJAX" will, difference being a "BUZZ" word will be missing.(I hope it wasnt obvious that I am not a fond of AJAX )
Or letting client side script control page movement or database access at all in a standard web application. Ajax isnt a buzz word its a methodology.
And besides, some ajax systems actually do use a hidden frame. I was merely offering a suggestion, maybe you should actually know what something means before bagging it out.
Well thats not how it seemed to me or I wouldn't have replied in such a way.
Thats what I gather from it and most of what im reading on it now seems to say that. How you do it doesnt really matter.
But really it doesnt matter anyway, I was merely offering a suggestion, not supporting or damning it. Your comment implied I meant more, I only replied because I didnt.