Re: [xml-policy] I have a question for you guys

Migrating this thread over to the spice-devel lists. If need be the thread 
should continue there.

The original intention was simply to make it possible for each application to 
have a separate policy declaration. So if we hosted applications A and B, 
then A could live under security restrictions X and B under restrictions Y.

The very original version of the code came from another platform distributed 
virtual environment I developed years ago which downloaded modules and 
allowed you to dynamically add/remove modules at runtime. It had to be secure 
because the platform would automagically download code when a user node 
connected to a server node.

Anyways all it does is load the policy data from xml. 

On Fri, 27 Jun 2003 05:02 am, Robb Penoyer wrote:
> I don't mean to bother you guys, you seem busy, but I have to
> ask. What's the history behind the xml-policy component? I
> mean, you probably wrote it with either an intended, or
> actual use in mind. I am interested as we over at ldapd are
> working out the research on security, and would like to
> understand/read anything about java security.
>
> An xml form of the policy is great, but I would like to
> understand the context for need....
>
> BU,
>     Robb
>
> BTW: Wiki looked like a Mac only product to me as well.
> serious bummer.

-- 
Cheers,

Peter Donald
----------------------------------------------------------------
Fools ignore complexity.  Pragmatists suffer it.
Some can avoid it.  Geniuses remove it.
-- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982
----------------------------------------------------------------



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php