True, but if EmbeddedNeo adds a shutdown hook for itself and I'd like to add my IndexService instance to that hook I couldn't and it won't do to just add another shutdown hook which just shuts down the IndexService because I have no control over the order those hooks are executed in.
2008/12/15 Emil Eifrem <e...@neotechnology.com>: > On Mon, Dec 15, 2008 at 2:58 PM, Mattias Persson > <matt...@neotechnology.com> wrote: >> It's a bad idea if you f.ex. have an IndexService which should be >> shutdown before the NeoService... but that's an issue we'll solve with >> events later on right? > > Right. And also, this would be a safe guard. The client would still be > encouraged to invoke "shutdown"' in whatever lifecycle mechanisms they > have for their app. Also, the contract with other components wouldn't > be affected -- you need to invoke shutdown() on every IndexService if > we automatically shutdown NeoService, and you need to invoke > shutdown() on every IndexService if we don't. > > But as you point out, with events reenabled the IndexService as well > can just do the Right Thing(tm). > > Cheers, > > -- > Emil Eifrém, CEO [e...@neotechnology.com] > Neo Technology, www.neotechnology.com > Cell: +46 733 462 271 | US: 206 403 8808 > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Neo Technology, www.neotechnology.com _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
