[Zope3-dev] More name game suggestions

[Phillip J. Eby]

At 02:35 PM 12/14/01 -0500, Shane Hathaway wrote:

>The intent of features is different.  You are supposed to create a feature 
>when you want to add capabilities to your application.  The 
>implementation, however, is the same.

So what if what you want is to adapt something to another interface?  It 
seems to me that many if not most of the applications of "features" in Zope 
really *are* just simple interface adaptation.  At least from my viewpoint.

Even the IPostal thing in the tutorial seemed to me like interface 
adaptation.  "I have some object, I need thing-that-does-X, so give me an 
implementation of interface X for this object."  I don't know and don't 
care whether this implementation is native to the object, "adapted" from 
another interface, or "added" because the object doesn't "support that 
capability".  I shouldn't *need* to know or care -- that's the whole 
*point* of having a registry for these things!

I like "adapter" because it's a generic usage that is easier to say than 
"implementation of an interface".  I would say "wrapper" rather than 
"adapter" except that it would detract from the uniqueness of "wrapper" in 
talking about how acquisition works.