using lightspeed in a web application

Hi, I'm looking for some resources (best practices) about how to use lightspeed in web applications.

I have currently some problems seeing how the I could use lightspeed when I have a web app where there may be several postbacks between loading an object from the database and storing the modifications back to the database. Specifically, in our web app, we have a workflow like this:

• The user navigates to a page to edit some object (e.g. a person). The object is loaded from the database and stored into the ASP.NET session.
• The properties of the object are displayed in an edit form (for the user to modify them)
• The user edits the object. This may cause several post-backs, therefore, the changes are only stored in the instance which is stored in the ASP.NET session, but not yet to the database.
• Finally, when the user clicks the "save" link, the object is stored back to the database.

I currently fail to see how this could be implement using the UnitOfWork concept/pattern, since we cannot prevent the postbacks during editing.
Are there any resources available that show how to implement something like that? Or do you suggest a different approach for it?

Thanks a lot for any help.

Hi,

With the approach you are using (and I may have misinterpreted it) you would need to do the following:

1. Load the object, store it in session
2. Do however many post backs are needed to get it into a valid state
3. When you want to persist the object ensure that you re-attach it to the unit of work. This step is critical as without doing it you will have problems (there is an Attach method you can use).
   

Another approach is to not store the object in session but maintain a reference to its ID somewhere (perhaps session, perhaps query string, perhaps hidden field, etc - just be sure to consider security here) and reload the object from the database, bind the values back to the object, validate and, if valid, persist it to the database. This will remove the need to re-attach as it will be attached automatically when you re-load the object each time.

I hope that helps, please let me know if I have completely missed the point of your question!

Thanks,

John-Daniel Trask