It's alleged Ken Foskey did scribe:
You could try closing STDOUT which will tell apache that your script has
stopped output.
This is interesting idea, I think I will give that a try if I can find
out how to get hold of the STDOUT file pointer.
In perl I executed a background task with an system( "command &" ); to
perform the background tasks. I then emailed a reponse to the client to
tell them the job was done.
That's the kinda thing I need to do. I was hoping to avoid doing a
system command because the action I need to do is easily done right away
in the php (database connection is already open with right privileges
etc). I just need to let the browser know that there's not gonna be any
more output, it's finished go and render the page and be happy. If I
call a system command I have to pass all the info I current have in the
application open a new connection to the database in the other process
etc. Doable but if I can just close the network connection that'd be neater.
Cron jobs aren't the go, this is an event driven task that needs to
happen when the event occurs, not some minutes/hours later when the cron
jobs wakes up at the specified interval.
Thanks
Pete
P.S if people reply to my email address it will probably block, just
reply to slug I'm subscribed
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
