Re: Session State Problem <<SOLVED>>
Sorry It was my own error, the key i provided back wasn't the same and when i fixed that another small problem (my own fault was caused).
Basically using Cache is a way of doing it, Cache(ITEMKEY) = VALUE
seems to work well
Re: Session State Problem
Why would you store anything in the global.asax?
Your approach may not be what you want. The moment the web server/service restarts, you lose your application variables/session variables/cache variables. A more prudent approach would be to store the details of it in a database, and then when a request for it comes up to :
1) Check the cache for this object. If it exists, server it.
2) If it does not, construct it from the data in the database, store it in cache. Then server it.
Re: Session State Problem
Yeah i wanted to store it in a database but i have to request my boss every time i want to create a database table, and have to justify why etc. She would have declined it for sure so using the Cache was the option.
The objects don't need to be stored forever, just so that serveral Javascript postbacks can use the same instance of a controller class which contains a document class which is to have attributes set on each postback.
Thanks for the help anyways.