G
Garry Freemyer
I've researched this question on internet, and I've tried a number of things
I found to no avail to solve this problem...
I work for a company using Visual Studio 2003 to maintain a website for
realtors.
This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.
There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.
Because of the default 20 minute timeout, the user ends up timing out before
they can submit the data because it is incomplete and so they try to enter
the next bit of data and rudely find themselves staring at a login screen -
all their data lost!
My boss sold them on an ISP on the strength of being able to setup the app
on their server and being able to solve this logout issue and your's truly
is now charged with solving this mess.
I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.
Nothing seems to have any effect but to waste my time and raise my fear
factor.
Any hints as to some real solutions to this problem would be appreciated. It
appears that the source of the problem is the server logging out users.
Thanks.
I found to no avail to solve this problem...
I work for a company using Visual Studio 2003 to maintain a website for
realtors.
This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.
There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.
Because of the default 20 minute timeout, the user ends up timing out before
they can submit the data because it is incomplete and so they try to enter
the next bit of data and rudely find themselves staring at a login screen -
all their data lost!
My boss sold them on an ISP on the strength of being able to setup the app
on their server and being able to solve this logout issue and your's truly
is now charged with solving this mess.
I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.
Nothing seems to have any effect but to waste my time and raise my fear
factor.
Any hints as to some real solutions to this problem would be appreciated. It
appears that the source of the problem is the server logging out users.
Thanks.