Maintaining the Session

7 Mar 2006 9:09 PM

kempshall

I have a web application that contains a Java applet that uploads and
downloads files between a client and server. My application is set to
timeout the current session after 30 minutes (i.e. in web.config,
there's <sessionState timeout="30">). Unfortunately, if someone is
uploading or downloading a file that takes more than 30 minutes, the
session times out. Is there any way to get .NET to recognize that data
is being transferred between the client and server and not timeout
unless there's 30 minutes without any data transfer?

Thanks,

Jay

8 Mar 2006 1:48 PM

Cowboy (Gregory A. Beamer) - MVP

Using standard web mechanisms? None that I know of other than further
extending the timeout, which has other issues. You could push the
upload/download functionality to a subweb that has a longer timeout, but that
just puts a bandaid on the problem.

Timeouts are the reason so many companies have gone to downloaders that use
something other than HTTP transfer for downloading their apps, updates, etc.
Moving file download to FTP is another option.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

Show quote

"kempshall" wrote:

> I have a web application that contains a Java applet that uploads and
> downloads files between a client and server. My application is set to
> timeout the current session after 30 minutes (i.e. in web.config,
> there's <sessionState timeout="30">). Unfortunately, if someone is
> uploading or downloading a file that takes more than 30 minutes, the
> session times out. Is there any way to get .NET to recognize that data
> is being transferred between the client and server and not timeout
> unless there's 30 minutes without any data transfer?
>
> Thanks,
>
> Jay
>
>