2010/8/29 Jeff Doolittle <[email protected]>: [...] > factory. Sessions are cheap to create. The rule is "One Session per > Application" (assuming you have one database you're working with) and > many, many, many Sessions.
Make that "one session _factory_ per application...", which I'm sure Jeff intended to write. :) /Oskar > --Jeff > > > On Aug 29, 4:22 pm, Kevin Anderson <[email protected]> wrote: >> What are the implications of having one session (managed by IOC) that >> is shared by the whole application? >> >> We have a WPF, MVVM application that originally used one session for >> each call to the repository, but found that we couldn't lazy load >> anything because the session was gone. We moved the session of the view >> model but found that in some instances a given object was being held in >> two different sessions. We then tried moving the session all the way up >> to the IOC and found that performance was fantastic. >> >> I am concerned that there will be negative impacts from having one >> session open for the lifetime of the application. >> >> Any thoughts? >> >> Thanks. >> Kevin > > -- > 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. > > -- 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.
