> On Tue, Oct 01, 2002 at 04:27:15PM -0400, Ryan Bloom wrote: > > On Tue, 1 Oct 2002, William A. Rowe, Jr. wrote: > > > > > At 01:12 PM 10/1/2002, Greg Stein wrote: > > > >For PHP, we said "make it a filter [so the source can come from anywhere]". > > > >I think we really should have said "for GET requests, allow it to be > > > >processed by PHP." The POST, PROPFIND, COPY, etc should all be possible to >handle by PHP, which means that PHP also needs a handler. > > > > > > Agreed, if you write a PHP script we better allow you to PROPFIND > > > or COPY the puppy, in addition to POST. > > > > These are two different statements, if I am reading both > > correctly. Please correct me if I am not. Will, you are saying that if > > we have a PHP script, then we need to be able to do all DAV operations on > > the script. Greg, you are saying that a PHP script needs to be able to > > satisfy a DAV request (meaning that the PHP code actually copies the > > resource, or generates the PROPFIND data). > > > > Assuming I am reading the two statements correctly, I agree with > > Will, but not with Greg. > > Why couldn't mod_dav be implemented in PHP? I see no particular reason why > not... Currently, PHP cannot because it is a filter, not a handler.
We have a switch in PHP now to handle mod_dav requests actually (under 1.3.x) There is no specific DAV support in there, it's just a switch that allows PHP to be a handler for things other than GET, HEAD and POST so people can implement whatever DAV stuff they want in userspace. -Rasmus
