Shane Hathaway wrote:
> Martijn Faassen wrote:
>> So, the only dependency cycles left in are these:
>> <--> <-->
> I fixed those tonight.  On the trunk, there are no longer any 
> dependencies between,, and 
>, except testing dependencies.

I should take a moment to describe the different purposes of these 
packages as I see them now.  Conceptually, they are really quite 

- A library of ZCML directives for configuring 
views.  Also provides generic view classes.  A better name for this 
package might be "zope.basicviews".  A lot of packages depend on this.

- Provides IPublication implementations and a 
mechanism/registry for choosing a different publication class for each 
request.  Most packages should not depend on this.  A better name might 
be "zope.publicationregistry".

- Provides generic views that translate HTTP verbs like 
PUT, DELETE, and OPTIONS into map operations.  The idea is clever, but 
not everyone needs a REST-style API.  A better name might be 

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to