Well that's partly true, Session Variables used to require cookies to be
enabled on the browser.  Now .Net has numerous methods for implementing
cookieless sessions
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspnet/h
tml/asp12282000.asp )

It's just a setting in the web.config file.  As far as the scalability
associated with using Session Variables to maintain state of an application,
I'm not sure what the limitation would be.  It may be my own inexperience
but I've never run into a situation where I couldn't maintain the state of
my user through a session variable, it becomes sticky when you start trying
to maintain state across disparate applications but there are options for
passing these variables through session id's or other similar structures.
Hope this helps and let me know if you have any other questions.

Tom Fuller

-----Original Message-----
From: Lindahl, Ron [mailto:Ron.Lindahl@L...] 
Sent: Thursday, August 08, 2002 11:12 AM
To: ASPX_Professional
Subject: [aspx_professional] RE: session state variables

From what little I've read, I have seen two recommendations so far.  You can
maintain session information on the server end in a database, or you can set
cookies.  The latter option of course requires the browser to accept
cookies.

Session variables work, but you may need to reset session level variables
with each postback.  I've seen session variables used to store information
temporarily between web forms, but I haven't seen any recommendation for
using them for maintaining application session state.  I have seen
documentation indicating they are not a great solution for this sort of
purpose because applications that use them have limited scalability.

-----Original Message-----
From: Thomas Fuller [mailto:TFuller@g...]
Sent: Thursday, August 08, 2002 8:37 AM
To: ASPX_Professional
Subject: [aspx_professional] RE: session state variables


Need to see some code because using session variables is definitely one way
to go about this.  You could also use a component of some type that would
check to see if a user is logged in on every page, then from that component
you could log there actions, this would give you the ability to do some
reporting later on, it's not a must, but it often becomes a very nice
feature to have.

Please send some code, I'm not much of a C# guy but your questions sound
more specific to web app development than C# syntax.

Tom Fuller

-----Original Message-----
From: Aasavari Gokhale [mailto:aasavarig@y...] 
Sent: Wednesday, August 07, 2002 7:51 PM
To: ASPX_Professional
Subject: [aspx_professional] session state variables

Hi everybody,

             I am developing a library web application
using asp.net and csharp. but since i am a beginner i
am not sure how to make the browser remember my user,
for eg if my user logs in, then he should be allowed
to use alll the other functionalities on my site like
checking ina  book, checking out a book, viewing a
list of all books etc. but how do i make the browser
maintain the user's session? also, i want to do
something like this that if the user doesnt log in,
then he cant access any of the functions on the
website.

can someone please help?

i tried setting the session["variable"] to some fixed
value once the user is authenticated and checked that
value in thepage load of all my aspx pages hereafter
but it doesnt work.

any help would be greatly appreciated.

thanks,
--Aasavari

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com