On Oct 12, 2009, at 4:38 PM, Joe Orton wrote:
On Mon, Oct 12, 2009 at 04:23:59PM -0400, Brian J. France wrote:
On Oct 12, 2009, at 3:57 AM, Joe Orton wrote:
On Fri, Oct 09, 2009 at 09:41:32PM -0000, Graham Leggett wrote:
--- httpd/httpd/trunk/modules/dav/main/mod_dav.h (original)
+++ httpd/httpd/trunk/modules/dav/main/mod_dav.h Fri Oct 9
21:41:31
+
+ /* return request record */
+ request_rec * (*get_request_rec)(const dav_resource
*resource);
+
+ /* return path */
+ const char * (*get_pathname)(const dav_resource *resource);
};
What is a "pathname" in this context? A URI path? A filesystem
path?
If the latter, what is get_pathname supposed to do for a non-fs-
backed
repository provider?
That I don't know, it could use bogus paths. I haven't gone down the
path of creating a new mod_dav_fs module, so I don't know exactly
how it
would work.
Well, there needs to be some API contract specified so that repos
backends can implement it.
So: why does the resource abstraction need to be extended to return
the
filesystem path? What will mod_dav use it for?
mod_dav_acl would use the filename to validate the acls. Like I said,
I don't know if get_pathname is needed or we should just use r-
>filename and make sure a mod_dav_fs_db module updated it.
Brian
