[PEAK] PROPOSAL: Remove ZODB/Zope X3 dependencies/"compatibility"

[Ulrich Eck]

On Sat, 2004-05-29 at 23:36, Phillip J. Eby wrote:
> I've been reviewing the latest version of Zope X3, and it appears to me 
> that it's a waste of time to keep chasing compatibility with it in peak.web 
> and peak.model.  So, I'd like to propose some changes to the affected packages:
> 
> 
> ZODB 4 and peak.model
> ---------------------
[snip]
> Anyway, this API should fix a lot of quirks and warts in the current 
> DM-based API, such as the inability to check whether an object "exists" at 
> retrieval time.  I'll probably write other posts later to flesh out this 
> design further, and the path along which the existing code will be migrated.

+ 1 ( +10 for eventSource integration )


> Zope X3 and peak.web
> --------------------
[snip]
> Thus, I believe we can end our dependency on Zope X3 for publishing 
> support, but the changes to peak.web will be substantial.  In addition to 
> the changes I've outlined above, we would also be dropping the use of 
> adaptation to convert components to their decorator/view objects.  We'll 
> still have decorators, but they'll be registered via the configuration 
> system instead, allowing "placeful" lookups, and getting rid of the need to 
> have the page, error, and traversal protocols for registration 
> purposes.  Indeed, we should end up with it being possible for most 
> decorators to be defined by simple configuration, without coding (as is 
> currently required).

+1 for that as well.

i'm willing to help here (as my time allows) if it is not more work to
design/communicate ideas vs. write code ;-)

Ulrich