Forum OpenACS Development: Re: Reactivating oacs-dav with file-storage?

Collapse
Posted by Gustaf Neumann on
The situation has not changed since 2015; according to docs, the current code of oacs-dav is not working for AOLserver or for NaviServer since at least 10 years (the see [1] for the details).

As stated several times, one problem with WebDAV is, that the various WebDAV clients built into several systems behave differently and even for one OS, these are moving targets. I've implemented in the past a fairly broad WebDAV support for OpenACS (5j ago), working for the Mac/Windows/Linux clients of that time, which was used by several groups in the learn@WU-system, but as we are a large organization, people use various versions of Windows/Mac-OS X/... various problems popped up due to changes bundled with the OS versions (people using older/newer versions of the OS, one has to configure the OSes with registry entries to work at all, etc.). Furthermore, problems popup up in complex cases, when user drag large folders, causing easily several hundred backend webdav queries for a single drop operation, which is a pain to debug.

... so, maintaining WebDAV is very costly. If the main goals is to upload many files with a single drop operation, one can use drop-zone in the xowiki menubar - with does not have the issues mentioned above.

-gn

[1] http://openacs.org/forums/message-view?message_id=4871430

Collapse
Posted by Frank Bergmann on
Hi!

Thanks! Good to know.
In the next version of ]po[, a priority will be the management for files related to projects.

However, a Web GUI is not enough for most Microsoft users. So my idea was to provide them with both Web and WebDAV access to "their" files, using the ]po[ project permissions to control access to files in a slightly modified file-storage package.

So we could limit access to WebDAV to Windows 7, 8 and 10 built-in clients. That would cover >90% of all potential users. Other users would need to receive an error message...

If I understand you right, this idea is basically unworkable, is that right?

Cheers,
Frank

Collapse
Posted by Frank Bergmann on
Just to be complete here on this thread:

I've recevied email with comments about oacs-dav:

- From Dave: There was a thread in February: http://openacs.org/forums/message-view?message_id=5348430 recommending to use the repository on SourceForge.
- From Iuri: The OpenACS 5.4.1 version of oacs-dav worked better for im.

@Gustaf: The funny thing is that file-storage has a dependency on oacs-dav, so it needs to be installed on basically every OpenACS system...

Cheers!
Frank

Collapse
Posted by Dave Bauer on
Would a JavaScript enhanced ui be acceptable? Windows webdav implementations vary greatly and are almost impossible to maintain support for.
Collapse
Posted by Antonio Pisano on
Another option might be to install some third party client/service that is more kind with the average webdav implementation. One example might be this https://cyberduck.io/ (no endorsement, just found by quick googling and tested briefly on our WIP, successfully)

One could also find something that has the same level of transparence of a "real folder", as e.g. davfs2 for linux http://savannah.nongnu.org/projects/davfs2 (this also seems to work with our code)

On my windows 7 vitual machine I could no connect the native webdav client not even with my owncloud, so it is some task indeed!

Collapse
Posted by Gustaf Neumann on
restricting clients is certainly an option.
Collapse
Posted by Dave Bauer on
Webdrive https://southrivertech.com/products/webdrive/ has historcally worked with oacs-dav on Windows, that might be an option as well. I haven't tested other clients.

Another thing we did was setup poatgresql based SFTP authorization from the openacs database with an external file storage location for the content repository and a trigger to add items to the database. You'd have to explore the security implications of that a bit.