Re: Long running CGI script

Does the user need to see the results or not? IE, do you want to show them the results or just say "Thanks, we're processing your input. Go away". If your users don't need to see the results, you could just make one scrip that handles the user interaction and another that handles the heavy-lifting, and have the user interface script kick off the heavy lifting in the background.

--Pileofrogs

Comment on Re: Long running CGI script

Replies are listed 'Best First'.
Re^2: Long running CGI script by ndnalibi (Acolyte) on Sep 16, 2008 at 13:24 UTC
The user will get a simplified view of the end result that looks pretty and they can check a random smpling of data to make sure everything looks OK. I am doing this with css using lower resolution images. The other end spits out a high res PDF with many thousands of pages. I can see this taking up to an hour. So your suggestion is basically what I'm looking for. I will take a look at the links and let you know my progess - I need to iron out a couple of image resize problems first. Thanks for the fast input!	[reply]

Replies are listed 'Best First'.

Re^2: Long running CGI script
by ndnalibi (Acolyte) on Sep 16, 2008 at 13:24 UTC

The user will get a simplified view of the end result that looks pretty and they can check a random smpling of data to make sure everything looks OK. I am doing this with css using lower resolution images. The other end spits out a high res PDF with many thousands of pages. I can see this taking up to an hour. So your suggestion is basically what I'm looking for. I will take a look at the links and let you know my progess - I need to iron out a couple of image resize problems first. Thanks for the fast input!

[reply]