Let me be a little more helpful here. global.asax is a class definition. The
global class is created at Application start-up, and it has a number of
event handlers (functions that respond to events) which can be defined in
it. As it is a class definition, you can also create additional fields and
properties which are static, and can be accessed by any page in the
application if you wish, although one should be careful of using static
fields, properties, and methods, by understanding what the implications of
such are (e.g. locking static variables when changing because they are not
thread-safe). In the global.asax class definition you can implement code in
the various event handlers that can store data in Application State, Session
State, data store, etc. These other classes exist in various scopes and at
various times. In addition, you have other opportunities to store data in
server-side memory, data store, or on the client, in the form of Cookies.
It may seem like I'm being picky here, but again, understanding what
something is, and how it works, is the key to being able to answer these
types of questions for yourself, which will speed up your programming
tremendously. Often, what seems like a "waste of time" in the short run,
saves you much more time in the long run, and that is what I'm trying to
help you to do.
To find out more about the global.asax class, you can visit:
http://msdn.microsoft.com/library/de...alasaxfile.asp
In addition, the entire Microsoft .Net SDK can be freely downloaded from:
http://www.microsoft.com/downloads/d...displaylang=en
I read it every day!
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"WJ" <Jo*******@HotM ail.Com> wrote in message
news:#s******** ******@TK2MSFTN GP12.phx.gbl...
I am attempting to use the Global.Asax to store my user's configuration.
Here is the concept:
1. User logs on into the site using Form Authentication.
2. I capture the user Credential, verify it and then assign this Logon ID
(user) a so called User's serverside cookie.
3. My system is configured to accept 1,024 concurrent users, this means
that my Global.Asax will host no more than 1,024 Logon IDs and their associated
cookies/variables. IOW, cookie is uniquely identified by its Logon ID
(visitor)
4. I understand that Global.asax does not travel to client PC, therefore
there is no concern about security.
My question is: Is the Global.asax a "good" place to track user's events
from page to page and back/forth between client and server ? I try to
avoid storing user's variables inside MS/SQL Server due to performance. I also
plan a scheduled job at night to down the IIS so that all Global.asax will
be refreshed.
Thanks for your help,
John
