Jon Stevens wrote:
>
> on 9/5/2000 1:19 AM, "Daniel Rall" <[EMAIL PROTECTED]> wrote:
>
> > I agree, but worry about people not knowing enough to differentiate
> > between the two. Jon, if you think that implementing the shutdown would
> > be straightforward, I would like to go ahead with that rather than see
> > this come up repeatedly. ;)
> >
> > Dan
>
> Sure, but you will need to do some work to implement this. I don't want to
> see people willy nilly adding stuff to Turbine.destroy(). I think there
> should be something in the Services architecture that allows people to
> register a method that gets called by the services architecture. Then, in
> Turbine.destroy() you should call the services.destroy() to shut all the
> services down.
I setup the destroy() chain that suggested here, then noticed that
neither DBBroker nor ConnectionPool implement the Service interface.
Two questions: first, should I make DBBroker implement the Service API
to take advantage of destroy() and cleanup its connections on shutdown?
Second, regardless of the answer to the first question, shall I commit
the destroy() chaining (Turbine servlet's destroy() method iterates its
Services, calling destroy on each)?
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
