> -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > > > So in this sense, Components ARE Services. But now the Avalon > > community had two names for the same thing and this is generally > > were confusion arises. > > I disagree with this. A "component" is an implementation artifact that > exposes 0..n services. A "service" is computation contract exposed by a > component. A component may include many other features that are not > exposed through the services that is publishes. > > A "service" is typically represented by a Java interface and possibly > supporting meta-info (such as a version, attributes, etc.). > > A "component" is an example of a "service-delivery-strategy".
Well, yes, IF you're taking about Merlin. The whole problem is that each container has used the terms differently. There are different definitions for component, container, service, kernel, block, meta-data, and so on for EACH container. While each definition is close enough that we don't get into too much trouble, it can be rather confusing. Part of the solution is to offer a history of the terms so that users can see how it was used then versus how it is used now. We then need to work on the documentation to insure consistency in use and definition. This is also the reason I started the Avalon Glossary: http://wiki.apache.org/avalon/AvalonGlossary > It's important here to separate out meta-info and meta-data. > <snip> I added your tables to the WhichContainer page in the wiki and moved my stuff to ContainerStory. I'm still working on both, but I think it would be good to finally have this stuff in the wiki or site so that we can point users to these docs rather than re-answering the questions every couple of months. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
