Forum Discussion
Kevin_Stewart
Oct 04, 2012Employee
I may not be completely clear on your objective, but you said that you don't want long running requests. HTTP traffic, by default, is fairly transient and I believe the typical TCP idle timeout is somewhere around 3-5 seconds. So i'm guessing you're talking about requests that include some amount of traffic that exceeds a given threshold (file upload, Ajax comet, etc.) I think in this case you could set an after timer at the beginning of each HTTP request, and then unset it in the response event. Then you could trigger an HTTP redirect or response if the timer expires. That may also trigger the timer if the response takes too long. And it wouldn't prohibit a lot of small requests.
Just a thought.