On Friday, August 9, 2002, at 07:42 AM, [EMAIL PROTECTED] wrote: > What I meant was something different. A directory in which components > can > publish their services can be helpful, like you said. > The interfaces I'm talking about are real roles that components claim > to be > able to play. So "client" means it can play a client in the way that > client was declared before (the protocol, which events are sent, ..., > see > below). Very similar to the interface that is spoken by the whole > component, > as outlined by the Emit: or "> .." "< ..." statements in your examples.
Which allows components to deregister themselves as necessary -- say, when you don't have any listeners connected, or if the service isn't configured, there's no point in being listed as a "music broadcaster" service (for example). I like the registry idea, too. Does that mean there'll be a component exposing a service called "component registry"? R.
