Forum OpenACS Q&A: oacs-dav with MacOS Snow Leopard

Collapse
Posted by David Spanberger on
HI!

I'm using oacs-dav to connect my MacBook with SnowLeopard to a file-storage. It works well with the exception that I can't upload files.

If I drop a file to the webDAV-Drive the file is created in the file-storage but no content is written in it. So the result is an empty file with the right name and mime-type in the file-storage.

The error.log does not show any error.

This problem does not come up on the Windows XP-build-in webdav client.

Does someone know a solution for this problem?

David

Collapse
Posted by Dave Bauer on
This is due to the fact that every webdav client existing implements the "standard" in a different way. There is a newer webdav client in AOLserver CVS that should support the OS X client better, but it hasn't been tested on newer OS X releases. This version is not integrated into OpenACS.

If someone is interested in funding the integration of the newer webdav implementation into OpenACS let me know.

Collapse
Posted by David Spanberger on
Hi Dave,
thank you for your answer. Could you please quickly summarize in how far the AOLserver implementation is enhanced compared with the implementation available in OpenACS? I understand, that the support for the old OS X client had been improved - are there any other additional features?

Thank you,
David

Collapse
Posted by Dave Bauer on
the tdav version in AOLserver CVS has apis to allow adding different storage and authentication backends. It doesn't require OpenACS, but could be added to OpenACS by creating the appropriate storage and authentication backend code to interface with OpenACS.

It has quite a few workarounds for the most common wedav clients that were in use when it was written. So the two goals were to make tdav useable with any AOLserver application and to provide support for Windows and OS X clients.

Collapse
Posted by Gustaf Neumann on
tdav from the aolserver cvs repository contains a the authentication code for aolserver and a webdav property handler for file systems. With that, one sould be able to install a plain aolserver with this module to share files in the filesystem of the webserver via webdav. The easiest way to checkout the feasibility for Mac OS X is simply to try this out.

tdav looks in general architecturally nice, with the only complaint that it could be done much more flexible object orientation in mind (subclassing e.g. of e.g. a general storage property manager etc.).

However, concerning Mac OS X, using this version of tdav would not solve the problem of the poster, since the Finder of Mac OS X (WebDAVFS) uses chunked encoding for PUT requests, which is not supported from aolserver/naviserver.

-gustaf neumann