[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Pnet-developers] Implementation of appdomain support
From: |
Tum Nguyen |
Subject: |
RE: [Pnet-developers] Implementation of appdomain support |
Date: |
Sun, 27 Mar 2005 00:41:23 +1200 |
> -----Original Message-----
> From: address@hidden [mailto:pnet-developers-
> address@hidden On Behalf Of address@hidden
> Sent: Friday, 25 March 2005 8:14 p.m.
> To: address@hidden
> Subject: [Pnet-developers] Implementation of appdomain support
>
> Hi folks,
>
> i'm working on the appdomain stuff and discovered that a number of
> elements
> have to be moved from ILExecProcess to the new ILExecEngine.
>
> The elements i am talking about are:
>
> coder, loadedModules, internalClassTable, stackSize, frameStackSize.
Anything that's not specific to AppDomains.
The coder, loadedModules, internalClassTable etc *are* AppDomain specific.
ILExecEngine will contain things like thread lists, appdomain lists as all
those are not specific to a single AppDomain.
>
> Pls. let me know if i'm wrong or i missed something.
>
> An other question (for the design) is:
>
> keep the API as is -> make a global variable to hold the engine pointer
> or change the paramlist of ILExecProcessCreate.
Global variable for engine with accessor function ILExecEngineInstance or
similar.
There will only be one engine per "OS" process.
>
> Cheers,
>
> Klaus
> ______________________________________________________________
> Verschicken Sie romantische, coole und witzige Bilder per SMS!
> Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>
> _______________________________________________
> Pnet-developers mailing list
> address@hidden
> http://dotgnu.org/mailman/listinfo/pnet-developers