On Jun 21, 2009, at 3:38 PM, Laurence Rowe wrote:
> Jim Fulton wrote:
>> I don't agree. The semantics are different. For example, you often
>> want to traverse to things in a template that you don't want to
>> expose
>> via URL. We currently (or last time I checked) expose ++resource+
>> +name
On Sun, Jun 21, 2009 at 9:38 PM, Laurence Rowe wrote:
> Jim Fulton wrote:
>> I don't agree. The semantics are different. For example, you often
>> want to traverse to things in a template that you don't want to expose
>> via URL. We currently (or last time I checked) expose ++resource+
>> +name in
Jim Fulton wrote:
> I don't agree. The semantics are different. For example, you often
> want to traverse to things in a template that you don't want to expose
> via URL. We currently (or last time I checked) expose ++resource+
> +name in URLs and this is a bug.
What use is a resource withou
Gaaa. As I did deeper, it's even more muddled that I feared. I'll
start a separate thread.
Jim
On Jun 21, 2009, at 8:48 AM, Jim Fulton wrote:
>
> On Jun 21, 2009, at 5:36 AM, Christian Theune wrote:
>
>> On Sat, 2009-06-20 at 13:04 -0600, Shane Hathaway wrote:
>>> Jim Fulton wrote:
Why?
On Jun 21, 2009, at 5:36 AM, Christian Theune wrote:
> On Sat, 2009-06-20 at 13:04 -0600, Shane Hathaway wrote:
>> Jim Fulton wrote:
>>> Why? traverseName is part of zope.app.publication's implementation.
>>> Now it's oddly split off in a very separate package.
>>
>> The publisher traversal code
On Jun 20, 2009, at 1:10 PM, Jim Fulton wrote:
> Why? traverseName is part of zope.app.publication's
> implementation. Now it's oddly split off in a very separate
> package. This makes customizing publication behavior more difficult.
> I recently made proxying overridable and missed trave
On Sat, 2009-06-20 at 13:04 -0600, Shane Hathaway wrote:
> Jim Fulton wrote:
> > Why? traverseName is part of zope.app.publication's implementation.
> > Now it's oddly split off in a very separate package.
>
> The publisher traversal code is very similar to the code in
> zope.traversing, so I
Jim Fulton wrote:
> Why? traverseName is part of zope.app.publication's implementation.
> Now it's oddly split off in a very separate package.
The publisher traversal code is very similar to the code in
zope.traversing, so I thought the best thing to do is put it in the same
package as zope.tr
Why? traverseName is part of zope.app.publication's implementation.
Now it's oddly split off in a very separate package. This makes
customizing publication behavior more difficult. I recently made
proxying overridable and missed traverseName.
This should be moved back to zope.app.publicati
