> I like the registry idea, too. Does that mean there'll be a component > exposing a service called "component registry"?
I'm probably off topic here but this brings to mind the idea of having component servers whereby an application could use a component that hasn't yet been invented. say I want to transfer a file. I've got a connection to a component server which offers an ftp component. the interface for file transfers is simple so whether the underlying component does the transfer via ftp or http, I don't know and I don't care. I make the same call. tomorrow someone builds a component that does file transfers but does it over http. my application, does a directory listing on file-transfer components and exposes the available feature set to the user. user could then see that file-transfers can be made over ftp or http because someone just put up the http component on the server yesterday. if user selects a transfer over http, the system will download the component from the server and use it. am I way out there? -----Original Message----- From: Richard Soderberg [mailto:[EMAIL PROTECTED]] Sent: Friday, August 09, 2002 5:30 AM To: [EMAIL PROTECTED] Cc: Rocco Caputo; [EMAIL PROTECTED] Subject: Re: Everything You Know Is Wrong (Object Systems Yet Again) 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.
