An alternative may depend. Conversation Per Business Transaction Session Per Web Request etc.
Tuna Toksöz Eternal sunshine of the open source mind. http://devlicio.us/blogs/tuna_toksoz http://tunatoksoz.com http://twitter.com/tehlike On Wed, Jul 8, 2009 at 6:52 PM, Maik <[email protected]> wrote: > > What is an alternative to this implementation?! > So I would say that in the correct sense of lazy loading that you have > one ISession which is always present! > > Right?! > > On 8 Jul., 16:52, Oskar Berggren <[email protected]> wrote: > > Because if you open and close the session in > > SomeRepository.FindSmthBySmth(...) you will not benefit from lazy > > loading, database transactions or session cache. These were just some > > quick reason that came to mind. > > > > /Oskar > > > > 2009/7/8 Dotan N. <[email protected]>: > > > > > Hi all, > > > > > I remember reading a post from Ayende that stated that if he sees code > where > > > someone opened session inside each persister method, he doesn't know > how to > > > use NH. > > > So after implementing various method to manage Session myself, and i've > > > steered clear of what Ayende recommended not to do, i've now exposed my > self > > > to linq2sql and > > > i couldn't see any special considerations to handle its form of session > > > there. > > > > > So what is wrong with opening session in repository? > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
