Re: [orion-dev] how to disable sandboxing?
I thought you were going to help us figure out how to solve this problem? Instead of re-iterating your original position, try to describe exactly what you'd like to be able to do, maybe even with example API, etc. Bug 393711 is a starting point, but you (and Simon) need to flesh out details, before we can think about implementing it.
Rafael Chaves ---2012/12/17 12:36:04---This bug report suggests sandboxing of plugins can be disabled: https://bugs.eclipse.org/bugs/show_b
From: Rafael Chaves <rafael@xxxxxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 2012/12/17 12:36
Subject: [orion-dev] how to disable sandboxing?
Sent by: orion-dev-bounces@xxxxxxxxxxx
This bug report suggests sandboxing of plugins can be disabled:
Could someone please shed a light on how sandboxing of plugins is
implemented in Orion and how it can be turned off (even if it requires
gutting some code in Orion)? I will then try to look into a way of
selectively disabling it (say, for plug-ins coming from the same
host/port), basically to address
https://bugs.eclipse.org/bugs/show_bug.cgi?id=393711. If my knowledge
could find it on my own.
I am hitting orion-dev because I think this is of architectural
interest. The differences between "built-in" and plugin code are an
overwhelming limitation in Orion as is today. It is either the case a
use case was foreseen in some extension point or it just can't be done
(usually because of sandboxing), and that seriously cripples
innovation on top of Orion.
You pointers/directions are appreciated. Keep up the good work.
orion-dev mailing list