[Zope] Opinions sought on acquisition issue

[Randall F. Kern]

BTW, I have a product called "CascadingFolders" that does exactly this.
If you need something like that let me know and I'll upload it to
Zope.org.

-Randy

> -----Original Message-----
> From: Chris McDonough [mailto:chrism@digicool.com]
> Sent: Thursday, March 29, 2001 6:33 PM
> To: The Famous Brett Watson; zope@zope.org
> Subject: Re: [Zope] Opinions sought on acquisition issue
>=20
>=20
> > The reason that this is an issue at all, however, is because
> > identically-named container objects to not acquire the=20
> contents of the
> > containers they mask, if any. The "images" folder in the=20
> "log" folder
> masks
> > the "images" folder at the root, thus *hiding* the contents=20
> of that folder
> > rather than *acquiring* the contents of that folder. What would the
> > implications be for Zope if acquisition meant that a failed method
> > invocation resulted in further traversal of the namespace=20
> stack instead of
> > immediate failure? Thus, if I try to reference=20
> "images['site-logo.jpg']",
> > and the first "images" object found does not contain=20
> 'site-logo.jpg',
> would
> > it be a good, bad, or ugly thing for Zope to *continue* the=20
> search for
> > "images" objects containing a 'site-logo.jpg'?
>=20
> It would probably be not so good.  It's my belief that we're=20
> trying to move
> to more explicitness, and this magic is hard to document. =20
> That's not to say
> that you can't make a container like this and hook=20
> __getattr__ and keep
> going!
>=20
>=20
>=20
>=20
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -=20
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>=20