If you want some help, you need to describe the solution you are trying to provide, not how you are having problems doing things that are not part of a recommended architecture using NHibernate.
It actually sounds as if a cache solution is what you require, but it is difficult to tell exactly from the problems you are encountering. What is the major use case for your application? John Davidson On Wed, Jul 21, 2010 at 1:34 PM, Giulio Petrucci <[email protected]>wrote: > Hi José, > > first of all, thank you rof your reply. > > On Wed, Jul 21, 2010 at 7:00 PM, José F. Romaniello > <[email protected]> wrote: > > Session, is not threadsafe. So the best (and only) practice is to not use > a > > session in multiples threads. Why do you need to use the SAME? > > Using different sessions I had this problem (which I posted about some > days ago): > http://groups.google.com/group/nhusers/browse_frm/thread/9bf83f97eed369de/5443d1bb4fe9a03d?hl=en&tvc=1#5443d1bb4fe9a03d > > Could you give me any hint? > > Thanks, > Giulio > > -- > > -- > 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.
