I will soon be developing an server application which will basically consist of a bunch of controller objects listening to MSMQ queues. Messages are then processed and then dispatched onto another queue. The processing part will be performed by a helper object located in an assembly which is loaded at runtime. We want to be able to update these assemblies dynamically - without bringing the service down. The obvious method is to host each controller in a separated AppDomain which can then be unloaded when we wish to update the processor assembly. However there will more than likely be 50+ controller objects, each running a different processor assembly, which means 50+ AppDomains.
Is this feasible? What will the implications for memory usage be? From my understanding the assembly which contains the controller class will have to be loaded into each AppDomain, is there any sharing of memory at all between AppDomains? Many thanks, Simon Jefford. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. http://www.messagelabs.com ________________________________________________________________________ =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
