I want your Suggestions on this and i want to implement this functionality in a better way. I have a list of records and it will contain 200 to 300 records or even more and the records is unique for each user. When the user select the records need to update the selected record from the list but that will not update the database only the list. So my question is : To hold the records temproarily what should i use whether i use Session or Viewstate or something different.
kindly help me out with this…
Viewstate has a big burden on requests and responses. I would say simply: don’t use that… for anything, in fact.
Session-state sounds more promising, but personally I’d be looking at using a database-approach here, even for the uncommitted data – just have some separate tables to represent the in-progress work, perhaps in a different db-schema, or an entirely different db.
I guess ultimately though, that is very little difference to using session-state (except: more formal). It is, however, easier to update individual records in a db than it is to load session, deserialize, edit the objects, serialize, and store as session.