On Fri, 22 Oct 1999, Mike Dameron wrote:
> Thanks for all the suggestions. Although these are all good suggestions, my
> main concern was not how to get the report to work but rather a way to have the
> oracle process killed if the user presses stop. Since the real issue here is
> not that the report runs so long, but that the query continues to run for no
> reason (since the results will never be seen).
How about this:
- Detach the process that generates the actual report and have this
process listen on socket X
- Have the server print a page to the user that contains a meta refresh
tag set to refresh once per minute (or 5 minutes or whatever). When it
refreshes and reloads the page, the script that generates the page sends a
ping to the detached process via the open socket.
I think you could also use server-push for this (instead of META tags) but
I know nothing about that.
- If the detached process doesn't get pinged at least once every X minutes
it quits.
It's a bit of a strange process but it should work. As an added bonus, it
allows you to generate an ongoing status report (as you've already done
all the work necessary to make that available, more or less)
-Dave
/*==================
www.urth.org
we await the New Sun
==================*/
