why not manage multiple session factories at once. each factory can be used within a given Domain Context. Castle has a facility to manage this with ISessionManager. If nothing else you can review the code and build your own.
On Jun 29, 3:02 pm, Oskar Berggren <[email protected]> wrote: > 2009/6/29 Mind Works <[email protected]>: > > > > > Hi, > > > Background: > > We have 1600 objects to be loaded in the session factory, thus > > impacting the memory footprint of the application. In the endeavor to > > reduce the memory footprint we are loading the objects dynamically > > where we are destroying the existing session factory and recreating > > one every time. > > Why does your ISession need to outlive the session factory? Why not > recreate it as well? The ISession should normally be fairly shortlived > anyway. > > /Oskar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
