W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1997

Jigsaw Shutdown Hook

From: Evan Coyne Maloney <emaloney@pencom.com>
Date: Mon, 14 Jul 1997 15:50:32 -0400
Message-Id: <>
To: www-jigsaw@w3.org
Hi, I sent the following message to the list last week, and received to
responses. I did a little more research into the problem and concluded that
there is no way to receive notification that Jigsaw is shutting down
gracefully. The problem is, we (my company) have written several extensions
to Jigsaw that spawn their own threads and run until Jigsaw exits, but that
need to cleanup after themselves. There are a few possible kludges, but I
think the best way to do it is to have Jigsaw have a hook that allows you
to be notified of shutdown.

For now, I've settled on the following kludge: I've extended the Exit
resource (w3c.jigsaw.status.ExitStat) so that it calls notifiers when
someone clicks on it. Of course, this means we have to replace the Exit
resource on every copy of Jigsaw that's running our extensions...not fun.

I think that this functionality would be a good addition to Jigsaw, so I'm
respectfully re-submitting my request for it.

>I've written several extensions to Jigsaw that do various things and need
>to be notified of the server's shutdown so they could clean up properly. I
>tried wrapping the w3c.jigsaw.Main.main() method in my own method so that I
>could do cleanup after the main() method exits, but I noticed that main()
>starts up the server asynchronously, and returns when the server is done
>starting up, not when the server shuts down. So:
>1. Is there a way to force Jigsaw's main() method to wait until the server
>shuts down before returning?
>2. If not, is there some sort of hook I can use to be notified when Jigsaw
>is shutting down?
>3. If not to that as well, may I be so bold as to request this feature? I'd
>be happy to do the coding for it myself, and pass it along.

Evan Coyne Maloney___________________________________________________
The two-legged air-breathing human.               emaloney@pencom.com
Received on Monday, 14 July 1997 15:50:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:31 UTC