Castle.NhibernateFacility and Castle.ATM Facility? But I'm with Diego, there is no value is abstracting the session scope management. Not to mention is simple to configure. environment open current session strategy dispose http begin request web end request service bus message arrive thread message complete rich client show form session per form* hide form
*this may require you're own implementation of ICurrentSessionContext but the idea is to associate the session to the form. On Aug 31, 10:55 am, Diego Mijelshon <[email protected]> wrote: > Don't. Session management is PRECISELY one of the things that should be > DIFFERENT for each architecture. > Web and WCF are similar though. Check uNhAddIns, there are some good > architecture ideas/examples/helpers there. > > Diego > > On Tue, Aug 31, 2010 at 11:21, Luka <[email protected]> wrote: > > Hi, > > I am trying to build an universal session manager that will work in > > these scenarios: > > WinForm Application > > Asp.NET application (web) > > WCF services > > > Is there any suggestion or is there any project like this one? > > > -- > > 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.
