But that way you're putting a risk that the container might be out of sync with the real state of the component. All that to save having an extra function. I would think the downsides are bigger than the cost of having an extra function to check the state of the component. Otherwise most people will implement that function but it won't be standard, reducing potential reusability, and causing pains to people who want to incorporate dynamic administration capabilities in the container.

Jonathan Hawkes wrote:
Yes.  An isRunning() method would not be useful to the container.  The
container knows whether the startable isRunning or not (ie: it has called
start() and not stop() ).

----- Original Message ----- From: "Yannick Menager" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 08, 2003 10:17 AM
Subject: Startable doesn't has a isRunning() interface ?




Is there any reason Startable doesn't has a isRunning() ( or something
like that ) interface ?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to