On Wednesday 11 August 2004 01:36, Alexis Agahi wrote: > On Tuesday 10 August 2004 19:00, Niclas Hedhman wrote: > > AvailabilityCapable (someone pointed out that xxxAware was used by > > WebWorks) is a 100% compatible change in all directions, believe it or > > not. > > Any idea about what would be this interface? > > Is it still an open discussion?
Under CTR, I committed the proposed interface to the repo when I made the suggestion. So, it is still called AvailabilityAware in the repo, but I am fully Ok with some other name. It has one method to signal that a component has disappeared, identified with the key used in the lookup() (ServiceManager), and also one method to signal that there is now a component available under that key in the ServiceManager.lookup(); void componentAvailable( String key ); void componentUnavailable( String key ); There is also a need for a UnavailableException extends RuntimeException, which will be thrown by the servicemanager.lookup() if a component is not available, and the SM is only allowed to throw that exception to capable components, otherwise revert to 'previous' behaviour. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
