on the thread time out, we had a shared server on a LAN and the http task was running an agent that returned something like a MB of HTML tables (for Excel display). We -had- to set our timeout to 180 seconds to let the agent complete.
That's a heavy load. If you have something that might take a lot of time, it makes sense to set this high. But, if performance -should- be good, and you have graceful failures (the user doesn't see errors or mangled pages) then a low setting should be fine, say 5 - 10 seconds max. Anything takes longer than that and people are tapping their fingers or clicking away anyway.
Hi Jake,
on the thread time out, we had a shared server on a LAN and the http task was running an agent that returned something like a MB of HTML tables (for Excel display). We -had- to set our timeout to 180 seconds to let the agent complete.
That's a heavy load. If you have something that might take a lot of time, it makes sense to set this high. But, if performance -should- be good, and you have graceful failures (the user doesn't see errors or mangled pages) then a low setting should be fine, say 5 - 10 seconds max. Anything takes longer than that and people are tapping their fingers or clicking away anyway.