views:

34

answers:

3

Hi

if u add this to web.config, then if a page have gone through long process, the client will not have a timeout exception.

<httpRuntime maxRequestLength="1024000" executionTimeout="36000"/>

they are timing out things for a purpose, what is it?, I tried to create a website with two pages I make a button in default1.aspx wait for 5 minutes. the other page requesting is not affected by that.

thanks

A: 

So clients can't tie precious server resources...

Frank V
Sure they can. They'll just make another request.
Josh Stodola
a long process like upload a file, will do that regardless you like it or not, isn't it
Costa
+3  A: 

not 100% sure I follow you but the purpose of a timeout is to ensure a client does not wait indefinitely for a response that may not come, it is part and parcel of working in a stateless environment.

Pharabus
+1 for mentioning stateless nature of the protocol
Josh Stodola
A: 

Request timeouts server-side are one thing, however IE and other browsers also have request timeouts. If you're performing something costly server-side use a status area instead of Request-Response to deal with processing.

Nissan Fan
what is status area
Costa