Re: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs

On Fri, 8 Feb 2008, Jonas Sicking wrote:
>
> So I had a couple of additional smaller inputs to this.
> 
> So first off, I'm not sure if the correct place to require 
> directory-wide policies to be place is "/foo/" or "/foo". Do both of 
> these from a uri point of view represent the directory resource? I know 
> servers redirect to "/foo/", but I think that's just to get relative 
> URIs in the default resource for the directory to be resolved correctly.
> 
> The question here is, which uri refers to the directory, is it "/foo" or 
> "/foo/".

It doesn't actually matter to the algorithm, by the way. Either could be 
used to set the policy.


> It seems like the current spec uses "/foo/" just to be able to do 
> substring matches. This seems like the wrong reason to make this 
> decision.

Unless I'm misunderstanding the spec, that's not the case. It certainly 
wasn't the case in my proposal...

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Friday, 8 February 2008 22:44:38 UTC