Let's imagine a use case like the one on chinook media manager: 1-The user pick an Album to edit. 2-The user edit the album 3-The user pick another album (go back to step 2). 3b-The user Save all edited albums. 3c-The user Cancel all. http://code.google.com/p/unhaddins/source/browse/trunk/Examples/uNHAddIns.Examples.WPF/ChinookMediaManager.Domain.Impl/AlbumManagerModel.cs
Why not use the Unit of Work that we already have?, the only reason is what Fabio point out Scalability. When you have too much users, you should opt for a UoW lighter (a custom viewmodel). 2010/1/5 Angel Java Lopez <[email protected]> > Hmmm... more context, please? specific use case? I'm talking about a web > application. > > > On Tue, Jan 5, 2010 at 4:29 PM, José F. Romaniello <[email protected] > > wrote: > >> Yes, I know one. The case of long sessions / business transactions. >> >> I want to call daoABC.MakePersistent(...) in the step 1,2,3,4. >> And if the 5th step fails, or the user abort I want to revert all. >> "Revert" means "abort", because using a long session mechanism the session >> is going to flush only at the step 5. >> >> However for web applications, I've used the Jason approach. For desktops >> applications, I've used CpBT (aka conversation per business transaction, >> from unhaddins). >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > >--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
