El 17 Oct 2008, a las 15:02 , Jim Fulton escribió:
First of all, its name is quite misleading. It should really be called 'zope.resolvepath' because it resolves TALES-like object paths. In fact, it's pretty much only used by the PageTemplate machinery to hook it up to the TALES engine (with one exception, see below).
Historical note. Until we decided to use the location framework and eschew traversal proxies, is was much more widely used.
It would be nice to deprecate zope.traversing and fold it into zope.app.pagetemplate.
+1
The request shouldn't really be necessary for this kind of path resolution, I think.
It's needed for looking up views and resources, both of which are commonly looked up in ZPT.
Yeah, I forgot about that.
The conditional multi-adaption sounds like a DWIM feature that I would consider one of our many mistakes that we made in the beginnings of our using the Component Architecture.
<shrug />
I'll note that the fix, in the context of ZPT is to always to a multi-adapter lookup using the request.
Right. I'm fine with it always being a multi-adapter look-up.