> -----Original Message-----
> From: Leo Simons [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, 01 April, 2001 21:47
> To: Avalon Development
> Subject: v4 jmx kernel
>
>
> I've been looking at the kernel, and to be honest, I find it
> a lot more complicated than it has to be.
>
> I think that for version 4, Main.class should be rewritten so
> that the Kernel is a Component with all the lifecycle methods.
+1
> This allows for easier jmx management (since it can simply
> be managed through the standard to-be-created default
> dynamic MBean).
..and easier remote management using CORBA. If the Kernel is a Component
I can easily wrap this and handle romote invocation of management controls
and notification by the Kernel to a remote manager (or delegated audit
server) of Kernel state changes.
Cheers, Steve.
> The class that creates the kernel would look like the file
> I've attached (it's non-working yet). Note: I'm not using a
> pipeline for creation of the kernel. I'm assuming this is not
> neccessary for security, though I'm not sure about that.
>
> thoughts?
>
> LSD
>
> <java:sig>
> About LSD = new PersonalInfo();
> LSD.name("Leo Simons");
> LSD.email("[EMAIL PROTECTED]");
> LSD.URL( [
> http://www.leosimons.com, // personal website
> http://www.atfantasy.com, // fantasy RPG portal
> http://www.the-sign.nl // web-design company
> ] );
> LSD.quote("Buh!");
> email.setSig((String)LSD);
> </java:sig>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
