Hello, I create my own class "User" and this User has lots of members/properties. I go to my login page and login - this login interrogates the database and instantiates my User class - I now have an instantiated object. I then want to keep the state of this
user throughout a few web pages without having to access the database on each postback, which is the best method to do this? Viewstate is not possible as it will be lost between different pages? What are the implications of storing an whole instantiated object
to session? I have noticed something called serialization - I believe I can take an instantiated object and all its data and save it to an xml file, then when the next page loads, de-serialize the data back into my object. What are the benefits of this? Could
I store this serialized xml to the database and would it be worth it, or just to a text file? - what would the security implications be of a text file? Thanks Calibra
calibra
Member
10 Points
2 Posts
Saving State of objects
Oct 08, 2003 11:32 PM|LINK
Patrick Y. N...
Member
505 Points
99 Posts
Microsoft
Re: Saving State of objects
Oct 09, 2003 05:19 PM|LINK
ASP.NET Developer
This posting is provided “AS IS” with no warranties, and confers no rights.