Originally posted by James Hodgkiss:
The db problem is being looked into, but I think having a timeout isn't a bad thing anyway.
Personally, I disagree.
I think the effort required to implement this would outweigh the benefits.
On my own site, I have a sample project for handling long running processes.
In it, after the first request is made, the app starts the task in a new thread and immediately returns a status page. The status page refreshes itself every
n seconds to see how the task is going. Once the task is complete, the app forwards to a results page.
http://simple.souther.us/not-so-simple.html See LongRunningProcess.
Something like that might work for you.
If after
n refreshes, the process isn't done, you could forward to an error page.