Hi Jerome and All,
A related question: Is there a programmatic way to tell the Restlet engine
to do a clean shutdown, and if so, what's the contract that it fulfills? I
see that there is an Application.stop() method, but I'm a little confused
about the purpose it serves. Code diving suggests it's treated as a kind of
callback facility that can be optionally implemented, but I can't find any
specific docs on this.
And one of the Steves suggested that a server should stop returning 200
status codes from its "happy page" during shutdown. Is there internal
support for this, or does it need to be implemented explicitly by me the
application developer?
Thanks for any insight!
Aaron
"Jerome Louvel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi Aron,
I suggest instead that you leverage the Tanuki Wrapper:
http://wrapper.tanukisoftware.org/
It provides you an Unix daemon that you can start/stop/restart easily and
many other features. We happily use it in production and it is also included
in the Restlet distribution.
Best regards,
Jerome
-----Message d'origine-----
De : news [mailto:[EMAIL PROTECTED] De la part de Aaron Crow
Envoyé : jeudi 6 mars 2008 20:28
À : discuss@restlet.tigris.org
Objet : Shut down a Restlet server using kill?
Is it ok to shut down a Restlet server using Unix kill? What
does Restlet do
in this case? And does anyone have any good advice on what
the application
code might do to handle this event properly?
