break in sessions

[Dave]

I have an asp app that uses session variables. The downside is if the
connection to the server is broken at any point during a user's session, the
user cannot get his/her data to the server.

I know that the user's form or data entry sessions should be shorter and the
user should be sending / saving data to the server often so that there is
less likelihood of losing a lot of data but do you have other suggestions?
For example parsing usernames and passwords in every send to the server - is
this likely to impact performance? Also, If the server or connection is still
down will the user know to just wait for the server to come up or the
connection to be established to try and resend when the first error appears.

Any suggestions of what a better solution might be?

Thanks in advance.

[Brandon]

Sounds like using cookies to just denote whether or not their login was
successful (and the user is currently logged in) is a much better way to do
things. Then they can leave and come back w/in the expiration time and still
be logged into the site if they were successful the first time.
--
KMG Software, Inc.
Thinking Beyond, Above, and Before
http://www.kmgsoftware.com
"Dave" wrote:

I have an asp app that uses session variables. The downside is if the
connection to the server is broken at any point during a user's session, the
user cannot get his/her data to the server.

I know that the user's form or data entry sessions should be shorter and the
user should be sending / saving data to the server often so that there is
less likelihood of losing a lot of data but do you have other suggestions?
For example parsing usernames and passwords in every send to the server - is
this likely to impact performance? Also, If the server or connection is still
down will the user know to just wait for the server to come up or the
connection to be established to try and resend when the first error appears.

Any suggestions of what a better solution might be?

Thanks in advance.

[clintonG]

ASP.NET 2.0 supports Profiles which can be thought of as persistent Session
variables as the data is written into the aspnet_Profiles table.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"Dave" <Da**@discussions.microsoft.com> wrote in message
news:2F**********************************@microsof t.com...

I have an asp app that uses session variables. The downside is if the
connection to the server is broken at any point during a user's session,
the
user cannot get his/her data to the server.

I know that the user's form or data entry sessions should be shorter and
the
user should be sending / saving data to the server often so that there is
less likelihood of losing a lot of data but do you have other suggestions?
For example parsing usernames and passwords in every send to the server -
is
this likely to impact performance? Also, If the server or connection is
still
down will the user know to just wait for the server to come up or the
connection to be established to try and resend when the first error
appears.

Any suggestions of what a better solution might be?

Thanks in advance.