[IronPython] Python in an AppDomain

DesLeo at gmail.com DesLeo at gmail.com
Wed Oct 22 18:53:12 CEST 2008


Howdy folks,

I apologize if this isn't really a Python question, but at the very least  
it's strongly related to the task at hand.

With the latest beta, running Python in an app domain is even easier than  
before, I'm totally loving it. I just have one question, when creating the  
low-security appdomain you have the option to pass in a list of fully  
trusted assemblies. I guess I don't really understand the implications of  
this, why does the appdomain need to have a list of those? At first I was  
adding the calling assembly to the list, but even when I don't do so I can  
still call on the runtime there without issues. My object model is kept on  
a separate DLL that accepts partial callers and wraps objects from my other  
assemblies for IPy, this seems to fit all of my requirements.

So I guess my question is, Is that option just beyond the scope of a simple  
IPy hosting scenario? I want to release the static class I'm using to  
manage the engine\runtime setup and I want to know if I should be allowing  
the option of externally rebuilding the sandboxed appDomain with  
user-specified trusted assemblies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20081022/a4574f14/attachment.html>


More information about the Ironpython-users mailing list