Hi, IMO, a JMX interface is primarily useful for an administrator who wants to monitor/manage a Resltet container, its connectors, its virtual hosts and of course its applications. Here is my candidate list: - ContainerMBean - ClientMBean | ServerMBean - ClientRouterMBean | ServerRouterMBean - VirtualHostMBean - ApplicationMBean
If we can have a hierarchy of MBeans, it would also makes sense to have RestletMBean (start/stop) and RouterMBean (scorers). Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Sean Landis > Envoyé : mercredi 18 octobre 2006 20:35 > À : [email protected] > Objet : Re: Restlets and JMX > > Piyush Purang <ppurang <at> gmail.com> writes: > > > > > Hi, > > > > The easiest way I see of integrating parts of restlet api is to > > declare the related MBean interfaces. > > > > The two interfaces that I see are: > > > > RestletContainerMBean > > RestletMBean > > > > Later we can consider RestletApplicationMBean. > > > > Or does anyone have another idea/approach? > > > > Cheers > > Piyush > > I think any component or restlet that has useful telemetry > and/or knobs is a > candidate for exposure as an MBean. The two above make sense to me. > > Logging control is a candidate. > > I'm not totally clued into how the scorers work, so maybe > this is inappropriate, > but tracking scorer behavior might be useful. Is this the > same as hit counts? > > Sean > > > > >
