Hi Tal,
When a call reaches a Restlet, this Restlet is automatically started if it
wasnt before. In your case, you need to detach them from the whole routing
chain.
Note that in recent milestones, we have implemented cascading start/stop
propagation. So when you start an application, it attempts to start the
whole routing graph.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org/
http://www.restlet.org
Noelios Technologies ~ http://www.noelios.com/ http://www.noelios.com
De : Tal Liron [mailto:tal.li...@threecrickets.com]
Envoyé : mercredi 24 février 2010 22:07
À : discuss@restlet.tigris.org
Objet : Re: Starting/stopping restlets
True.
So, I guess the only way to remove turn off routes/restlets is to detach
them?
On Wed, Feb 24, 2010 at 2:33 PM, Stephan Koops stephan.ko...@web.de wrote:
Hi Tal,
you could do some initialization and finalization work in your own Restlets.
best regards
Stephan
Tal Liron schrieb:
This is a basic attribute of any Restlet, but it seems like nowhere in
the framework is it used.
My expectation was that routers, filters, etc., would not pass requests
on to a stopped target restlet. However, it seems that stopping restlets
has no effect.
Is this by design? In which case, what is the purpose of
starting/stopping?
-Tal
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2451
685 dsMessageId=2451685
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2452511