Re: [Zope-dev] split out zope.component "mechanics" into a separate package (was Re: improving the utility and adapter lookup APIs)

2009-11-28 Thread Martijn Faassen
Chris McDonough wrote: [snip] > It tries to address the following problem. > > Currently people seem to get wrapped around the axle and confused by the > purpose of "the ZCA", which currently implies at least two different things: > > - Machinery to perform complex registrations and lookups usin

Re: [Zope-dev] split out zope.component "mechanics" into a separate package (was Re: improving the utility and adapter lookup APIs)

2009-11-27 Thread Chris McDonough
Martijn Faassen wrote: > Chris McDonough wrote: >> Chris McDonough wrote: If some set of ZCA APIs made it the responsibility of the *caller* to invoke the adapter with arguments would go a long way between normalizing the difference between utilities and adapters (because the

Re: [Zope-dev] split out zope.component "mechanics" into a separate package (was Re: improving the utility and adapter lookup APIs)

2009-11-27 Thread Martijn Faassen
Chris McDonough wrote: > Chris McDonough wrote: >>> If some set of ZCA APIs made it the responsibility of the *caller* to >>> invoke >>> the adapter with arguments would go a long way between normalizing the >>> difference between utilities and adapters (because they would essentially >>> then

Re: [Zope-dev] split out zope.component "mechanics" into a separate package (was Re: improving the utility and adapter lookup APIs)

2009-11-25 Thread Gary Poster
On Nov 25, 2009, at 5:08 PM, Chris McDonough wrote: > Chris McDonough wrote: >>> If some set of ZCA APIs made it the responsibility of the *caller* to >>> invoke the adapter with arguments would go a long way between normalizing >>> the difference between utilities and adapters (because they wo