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). 2010/1/5 Angel Java Lopez <[email protected]> > +1 for Jason approach. > > Any case to use long running NHSessions in an ASP.NET (MVC or not) > application, that could not be resolved via Jason approach? > > Angel "Java" Lopez > http://www.ajlopez.com > http://twitter.com/ajlopez > > > On Tue, Jan 5, 2010 at 3:48 PM, Jason Meckley <[email protected]>wrote: > >> +1 for Fabio. >> >> There are quite a few posts about this actually. Personally I don't >> like the idea of long running sessions. I keep a 1:1 ratio with >> requests and sessions. .... > > > > -- > 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.
