[Zope3-dev] Associations

[Gary Poster]

From: "Roch'e Compaan" <roche@upfrontsystems.co.za>
> I'm surprised the ZPatterns framework hasn't surfaced more in the Zope3
> discussion, glad that it does now :)

(Someone correct me, but) I believe both the Zope3 coders and ZPatterns'
creators are moving away from supporting the ZPatterns framework itself, and
towards, in the very heart of the code, the basic design pattern on which
ZPatterns is based.  Similarly, Phillip J. Eby has moved to TransWarp, and
talks about it and Zope3 here a bit:
http://lists.zope.org/pipermail/zope3-dev/2001-December/000268.html

> Anyway, does it make sense to have multiple proxies for a single Dataskin
> instance?  If it does then I don't think there would be a problem.

To answer your specific question, Steve's proxy idea, at least as I
understand it, is that it would be divorced from the rack, in a sense--the
rack wouldn't control or even keep track of the proxy's existence.
Therefore one could have multiple proxies for a single rack-mounted object.

I'm writing up a proposal for this, and will try to put it up on the
fishbowl by the end of the week for everyone to pick at.  I need to design
an associations system that can associate "real" Zope objects with one
another.  Ideally, it could also associate with ZPatterns/TransWarp-like
objects created from dataskins.  I think I've come up with something that I
can use that specifically incorporates this, but in any case the underlying
pattern would be the ZPatterns rack pattern, probably with specialists and
the rest.

Thanks again to Steve for the good idea.

Gary