Anyway its not like Session variables are available for
sometime and not available for sometime.
When your session starts it is very much available unless
your session ends
One more thing Session variables can very much be used in
Application events
If u explain ur question with a small illustration may be
i can try to figure out your question and try to give reply
-----Original Message-----
OK, can someone provide me with a logicaland architecual reason whythe Session object is only available sometimes??? OK, I understandwhy BEFORE the Session_Start event happens that a session object can'texist, but why not in other events? OK, OK yes on the FIRST requestever, maybe the session object wouldn't exist in
Application_BeginRequest or Application_AuthenticateRequest but let'sface it, after the first request, we all know Session_Start HAS tohave been hit, so the session object does exist! So why can't we getat it in all these application events? Can someone please tell me 1)The logical reason why the Session object (which uh, I think, issuppose to track the entire http session) kind of comes and goes inasp.net and 2) the architectual reason why this behavior has to be.I'm getting fed up trying to figure out when the session object canand cannot be used (please, no diatribes why session object should notbe used) and why 'events' don't seems to understand that other'events' have happened.
.