another common approach is session per form with thick client apps. you would have multiple sessions open on the UI thread.I would recommend 1 session per use case. how you define a use case is up to you, it's common to align a use case to a web request, thread or windows form.
On Nov 29, 9:28 am, Lee Robie <[email protected]> wrote: > I see that it’s fairly typical to have multiple ISessions open at a time, > with one per thread. > > My question: are there use cases where you would want to have two ISessions > (for the same database) in the same thread open at the same time? This would > of course imply two first level caches. > > I know this comes up, for example, when using IInterceptor to implement > audit logging. Are there any other corner cases or common cases where two > open sessions are needed? > > thanks, > > - lee robie -- 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.
