-----BEGIN PGP SIGNED MESSAGE-----
Michael Howitz wrote:
> after thinking the problem over at gocept we came to the following
> - A site is a place which gives acces to a component registry.
> - ISite isn't a good name for the concept behind it, because it is
> connected too tight to a website and on having hierarchical
> structures (at least in the code).
> - In long term a more abstract concept for ISite could be added.
It is a "place", in the classic Zope2 sense, as implied by "placeful" /
"placeless": a location-specificpolicy configuration point, which can
acquire further policy configuration from "above".
In Zope2, nearly every persistent object is a "place", at least for
purposes of configuring security.
> - In short term, for cleaning up dependencies, I propose to move
> ISite to zope.location, because it is the only package outside of of
> zope.app.* which uses ISite and defindes a method to get the nearest
> site. We think this is the right place because ISite is about
> component registries in the context of location.
> - zope.app.component.interfaces then can import ISite from the new
> place to avoid deprectation.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list