To all prospective developers:
Let me explain what the Enclosure can currently do, what is broken, and then what we need going forward.
Install, and uninstall modules, by command. (using jxl.enclosure.Modules)
Locate other Enclosure peers on the network, download modules from them and install the modules, dynamically.
Enforce security rules using the jxl.enclosure.security.* classes.
Store and recall user specified security polices to enforce on modules.
The ability to graphically review and change user specified security polices (jxl.enclosure.Policies, jxl.enclosure.security.gui.*)
Refine the default security policies by modifying jxl.enclosure.security.ForbidenPermissions and adding a GrantedPermissions class.
Create a means of quickly testing an Enclosure module so that it is easy to develop or port an application to Enclosure.
Generally test the system by installing and using existing apps in Enclosure.
I really want to use a stripped down version of Beanshell to perform the basic admin operations for Enclosure: things like install, uninstall, update, view policies, and even as an interactive app launcher. If this were done we could drop all of the main-classes like Modlues, Policies, Main that do this work. This will be a complicated process involving security, access control, and reflection.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.