In a WEB app you can use CpBT in the same way of a desktop app. The matter is scalability. CpBT may work well in WEB where the amount of concurrent users is less than 1K and, btw, outside a web-farm. I'm sure you know the consequence of a fat HttpSession (in web CpBT will use the HttpSession for the conversations-store).
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. > > -- Fabio Maulo--
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.
