Fabio
I totally agree wiith you that serialization wont help me in reducing
memory. All I am trying for is following
Currently NHibernate loads all assemblies when the code does
config.addassembly("assemblyname") . It goes thru all the assemblies
and starts validating hbm.xml file so on so forth . But the fact
remains that those assemblies stay lingering around till the
application life time which adds to the memory footprint. All I was
trying to do was to do addassembly and build config object in
different APPDOMAIN and unload it once I have passed the config object
back to default config object. This would help us reduce the footprint
of loaded assemblies which are not required anymore. But when I try to
getdata /setdata it gives me serialization error for "config"
object ...hence serialization
On May 4, 6:10 pm, Fabio Maulo <[email protected]> wrote:
> 2009/5/4 codegoblin <[email protected]>
>
>
>
> > In that case I will be touching the source code of NHibernate and what
> > would be the things required to do if we change NH source code
>
> > 1. I would have release NH 1.2.1 with the patch ?
>
> No.
>
>
>
> > 2. Does that make my app vulnerable to be part of open source as well
> > according to LGPL?
>
> No, if you make the patch public or the project fork public.
>
> Btw, the serialization is not the solution for memory size.
>
> --
> Fabio Maulo
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
