Re: HTTP_WebDAV_Server Proposal

+1 = even though I got my own :) Note ot add somewhere: Windows web folders sends a PUT with '0' bytes to create the file, then gets it to check it was made, then writes the full data.. - probably worth noting if you implement stuff.. I've still got to test linux's davfs, - got the modules working, but need to debug the socket connection.. Just for an interesting read: most of the development is done using tcpbug 80 192.168.1.x 81 and running apache on port 81. that way You can check what is getting sent to the server (eg. a working apache mod_dav), and emulate it in php. (as the RFC is not that well written = compared to something like the SMTP RFC) Christian chose the array return method, = and took my example of extending the base dav class :)... I've taken the approach of 'intelligent files/collections = mapped to DataObjects' which have a 'webdav interface' to cope with move, copy, and webDavGetProps stuff... At the moment my webdav stuff is tied up with a Mini Framework (eg. mapping of url's to objects), which is still a little way off being pearified... or even documented properly... anyway great work, Regards Alan Christian Stocker wrote:

Hi WebDAV is coming to PHP (at least it will be possible with 4.3). Therefore hartmut holzgraefe took my proof-of-concept WebDAV Server class written some time ago and developed it much further and i think, now is the time to put it into PEAR :) It's not pearified right now, but we'd like to use CVS server to allow concurrent developement (we can put it on our cvs server as well, if the PEAR folks think, we have to pearify it first, but i think PEAR is the better place..). Does anyone object, if we commit that thing? One main issue I have right now is the naming. I think HTTP_WebDAV_Server is the most appropriate. Or do you have other propositions? chregu