Re: Issue #3242 is heating up.

> I haven't reviewed the patch, but I think the idea of having looser
> restrictions on when we return OPTIONS is valid.  IIRC, the response
> to OPTIONS is per-repository, meaning that it won't change depending
> on which path the user is accessing.  It sounds like the cause of
> #3242 is an unfortunate interaction between common parent reparenting,
> and the OPTIONS stuff introduced in 1.5.  Perhaps this is a creative
> way to solve it?

Well, PROPFIND is also impacted by this. If you solve the OPTIONS
thing, you end up getting caught up at PROPFIND. As for being
creative, I think Mike's suggestion to improve our authz framework
would be that creative way to solve. We can accomplish two things at
once and still not change the performance improvements we get by the
new reparenting approach.

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2358845