> > “one uow = one session = one transaction” I can agree with. But “Http > request = one uow” can be a real issue, especially when acting as a > “front end” for a highly distributed environment. Each “Back end” element > often needs to be a uow, with all of them (possibly some succeeding, some > failing) in one HTTP round trip. >
That was what I meant with a composited interface. All items in the view are seperated components. You don't know where such a component would fetch its data from. It could be directly from a database, from a out of process key/value store, from an internal cache, from a db via an ORM or from a remove service. For this reason I would not try to re-use a session. Just let each component create its own session and dispose it as it is probably not needed for all components to share the same transaction. Afterall, these components are completely autonomous so these should not share anything if possible. Ramon -- 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.
