SabreDAV 0.3
Just got a new alpha for this WebDAV library, this version mostly contains bugfixes, and:
- Makes use of gzuncompress() instead of gzdecode()
- Support for Smultron temporary files.
- Now a pear package and also has a phing build script.
I found it hard to figure out all non-standard behaviours for the common WebDAV clients, as there wasn’t a lot of information to be found on the net. I documented all my findings, which could perhaps be of use for other implementors of the protocol. I’m hoping this will become a good resource for this stuff.
The package is still very much alpha state. Theo reported a segmentation fault while running the package on OS/X + Apache2 + PHP 5.2.5. My own testing environment is Debian Etch + Apache 2 + PHP 5.2.0-8+etch11, and I got some good results there.
Comments
stephan •
very nice!works like a charm here...
will there be hooks for custom actions on get/put/delete/... ? or do i have to extend a class for this?
Evert •
Hi Stephan,To extend the webdav service with your own business logic, you have 2 choices. You can extend the Tree class, which basically gives you a method for every operation, or you can use the ObjectTree and create your own File and Directory classes.
An example of how this is done can be seen in the FS/ directory.
stephan •
Ok, that's fine for me.Another thing, how can I contact you for bugs/feature requests? Maybe you can set up a forum or a mailing list...
SabreDav works like a charm now, but I needed 2 hours to get it running - php on gentoo linux hasn't got XmlWriter compiled in by default, you should check for this extension on runtime...
Evert •
Hi Stephan,Not a bad idea to have an alternative when xmlwriter is not there..
Bugs can be reported here: http://code.google.com/p/sabredav/issues/list
And there's a mailing list: http://groups.google.com/group/sabredav-discuss
2 hours is a bit over the top, yes.. lets see if we can shorten this.
stephan •
Debugging webdav sucks, i know that now ;-)What saved me was a telnet session to the webdav server, and there was the XmlWriter error ;-)
Evert •
I can highly recommend a debugging proxy.. I tend to use Charles for this, its invaluable!