Hi Sidar Our idea was to load up the appdomain and get the config part done with which also involves loading of assemblies which stay in memory and are a resident of memory for application lifetime. So if i could do this in another appdomain with some extra startup time and then unload it I would be reducing some of memory footprint.
On May 4, 3:43 pm, Sidar Ok <[email protected]> wrote: > Keep in mind the breaking changes from 1.2 to 2.1 > > @codegoblin > > Can you expand on how you want to use config serialization to reuse configs > in different app domain ? Is it that you only don't want to pay the cost of > reading the config again upon each AppDomain creation ? I see a lot of > problems with this approach if that's the case. > > > > On Mon, May 4, 2009 at 11:29 AM, Tuna Toksoz <[email protected]> wrote: > > 2.1 will be out, so I believe you can use it in your project and assuming > > that your project takes some time till its release, nh will be out so it > > shouldn't be a rpoblem. > > > Tuna Toksöz > > Eternal sunshine of the open source mind. > > >http://devlicio.us/blogs/tuna_toksoz > >http://tunatoksoz.com > >http://twitter.com/tehlike > > > On Mon, May 4, 2009 at 9:40 AM, codegoblin <[email protected]> wrote: > > >> Having said that is it a good idea to move towards NH 2.1 and use 2.1 > >> trunk code in production? > > -- > Sidar Ok > > http://www.sidarok.comhttp://www.twitter.com/sidarok --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
