I agree with your plan .. I rather like the automatic service discovery.
#x27;origine-
> De : Piyush Purang [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 22 octobre 2006 14:42
> À : discuss@restlet.tigris.org
> Objet : Re: Restlets and JMX
>
> One thing common to all the following approaches is to define common
> baseline Management interfaces to th
f the router/scorer duo in the
future :-)
Best regards,
Jerome
> -Message d'origine-
> De : news [mailto:[EMAIL PROTECTED] De la part de Sean Landis
> Envoyé : vendredi 20 octobre 2006 20:57
> À : discuss@restlet.tigris.org
> Objet : Re: Restlets and JMX
>
> Hi J
[EMAIL PROTECTED]
> Envoyé : jeudi 19 octobre 2006 23:51
> À : discuss@restlet.tigris.org
> Objet : Re: Restlets and JMX
>
> Okay here are the results of my first test with JMX integration
>
> I was able to stop the container but when I try and start it
> again ...
>
Hi Jerome,
>
> Scorers are involved in the call routing process. Each scorer attached to a
> router is acting as a routing option. The router decides on the option to
> follow by computing a scorer for the call with each scorer and applying a
> selection algorithm (first match, best match, etc.).
Okay here are the results of my first test with JMX integration
I was able to stop the container but when I try and start it again ...
I get an "address already bound" exception
So that means stop doesn't stop all connectors which makes sense but
then why does start try and start a new connector
Hi Pyiush,
> What about lifecycles? It is nice to be able to document lifecycle of
> a restlet and container etc...
This would be centralized on RestletMBean because the Restlet class has the
start(), stop(), isStarted() and isStopped() methods.
> Then we can expose status through the MBeans
Hi Sean,
> 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.
Agreed.
> Logging control is a candidate.
Actually, in beta 19, the call logging (writing a file similar to an HTTP
log) will be c
Hi Jerome,
What about lifecycles? It is nice to be able to document lifecycle of
a restlet and container etc...
Then we can expose status through the MBeans ... and ways (operations)
to transit from one state to another.
Looks like a comprehensive list and I don't see why we can't have a
hierar
is
> Envoyé : mercredi 18 octobre 2006 20:35
> À : discuss@restlet.tigris.org
> Objet : Re: Restlets and JMX
>
> Piyush Purang gmail.com> writes:
>
> >
> > Hi,
> >
> > The easiest way I see of integrating parts of restlet api is to
> > declare the
Piyush Purang 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
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
12 matches
Mail list logo