Leo Simons wrote: > my name's not Peter, but.... > > 1) On the server side, there are various components that are exported > to an MBeanServer. This needs some refactoring 'n stuff, but the > basic idea is there. Peter or I will probably get to this pretty > soon. > > 2) Then there needs to be a thin http server layer which maps commands > received over http (using POST, probably) to commands to the > MBeanServer, and sends the results back. > > 3) On the client side, you need what the JMX spec calls an adapter. > We're doing this over http as that is by far the easiest. This > is a standard-issue html client that talks to the aforementioned > thin http server.
I've downloaded the JMX stuff from Sun. But haven't had time to look at it yet... > 4) we need some simple security measures implemented in 2 & 3. > The server should check whether the client is from the localhost. > If it is not, a uname/password should be provided by the client > (probably using http_auth). Sounds good. For our purposes I think we'd want an SSL option too. > There are some utility classes to help with (2) in the phoenix cvs > under /console/src/java, and a mock http client under /console/src/mockui. > > Any help is appreciated a lot (we've been kicking the beastie for > a while now); send your engineer over to the Avalon Phoenix > Developers List and we'll hammer it out :-) OK - He (or I) will be available in a few days if all goes well. Meanwhile we can start some reading - thanks. PT -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
