[CalendarServer-dev] Re: [CalendarServer-changes] [1345] CalendarServer/trunk/lib-patches/Twisted/twisted.web2.dav.resource. patch

Wilfredo Sánchez Vega wsanchez at wsanchez.net
Fri Mar 9 09:50:46 PST 2007

   It's true that resources looked up via the "fast path" in the  
directory hierarchy are not cached, but I don't know why this is broken.

   Only resources looked up through the request are cached, and anyone  
calling urlForResource() has to be aware of that.  So don't call  
urlForResource() on a resource you obtained by other means.  In the  
case of principal resources, call principalURL().  It has always  
worked this way.


On Mar 8, 2007, at 8:53 AM, source_changes at macosforge.org wrote:

> With the update to the new Twisted branch, urlForResource now raises  
> an exception. We need to trap and ignore this.
> However, this whole urlForResource thing is now broken as resource  
> can be found without going through locateResource
> when using the directory services thingy - lookups there do not  
> depend on the request object and thus do not cache
> a urlForResource. This needs to be fixed one way or another.
> One option would be to have urlForResource be a method on the  
> DAVResource object that defaulted to calling the request
> implementation. Then we could override that on our directory related  
> resources and have then return their "hard-coded"
> uris.

Wilfredo Sánchez - wsanchez at wsanchez.net

More information about the calendarserver-dev mailing list