[Zope3-dev] Re: capi vs zapi

[Philipp von Weitershausen]

Stephan Richter wrote:
> On Friday 04 March 2005 13:23, Garrett Smith wrote:
> 
>>I noticed the new 'capi' -- when should this be used instead of zapi?
>>I'll add that info to changes.txt if any cares to enlighten :)
> 
> capi is a short form for zope.component and should only be used when zapi 
> cannot be used. For example, you cannot use zapi in zope.app.traversing, 
> because this package is part of zapi. Another use case is when you develop a 
> package that does not depend on zope.app, then you must use the component API 
> directly.

Of course, you're totally right on when to zope.component and not zapi. 
However, I think calling it 'capi' dilludes new developers (and even 
Garret here) into believing we're dealing with some sort of different 
API, while in fact it's just zope.component. As I've said in a post to 
Garret's checkin msg just a minute ago, we should replace 'capi' with 
'zope.component' for clarity at least in doctests...

Philipp