It would be good to reconcile whatever that AOO code is attempting to do and
the WebDAV locking model, specified now in RFC4918,
<http://tools.ietf.org/html/rfc4918>. (There is a locking-related Errata item
as well.)
There is an extensive treatment of how much discovery and negotiation might be
required, and how much is going to be a function of server-side
implementation-dependent behavior. Whatever is done, it clearly should not be
an overlay on WebDAV that only works when everyone is using a (matching) AOO
release to access a WebDAV-stored document.
The WebDAV mailing lists are pretty quiet these days (or my subscription has
lapsed). That might be a good place for further clarification, if needed.
That's an interesting task. Good luck and thanks for looking into it.
-- Dennis E. Hamilton
dennis.hamil...@acm.org +1-206-779-9430
https://keybase.io/orcmid PGP F96E 89FF D456 628A
X.509 certs used and requested for signed e-mail
-----Original Message-----
From: Giuseppe Castagno [mailto:giuseppe.casta...@acca-esse.eu]
Sent: Thursday, December 4, 2014 02:49
To: dev@openoffice.apache.org
Subject: Spam (8.02):[DEV, WEBDAV] About issue i125194 and file lock under
Webdav
Hi all,
it's some time I don't write to the list, but even though I last coded
for AOO (was OOo then and some years have elapsed...) I continued to
follow the project all along.
Anyway, I'm writing about issue i125194 [1] because Davide Dozza
discussed the problem with me and I decided to have a look into it,
trying to provide a patch.
I studied part of the involved the code and I found that some of the
needed code is already in place, but it seems that the final
implementation of the lock mechanism for webdav [2] is not fully
implemented.
Some questions:
1) I need some explanation on the way the webdav file lock is supposed
to work. In webdav content provider [3],[4] or somewhere else?
2) currently the file lock mechanism is implemented in module sf2 using
a dedicated hidden file [5], are other mechanisms for it?
3) I found a property named IsReadOnly, checked here [6] but nowhere
this property is managed aside from receiving a default 'false' value.
Was this prepared for the lock mechanisms managed somehow in module ucb?
Of course I need to know if I'm talking nonsense on the above
points :-).
My set-up to debug AOO:
Linux Ubuntu 14.04
emacs and gdb to edit and debug
I submitted a ICLA to Apache Software Foundation on Apache Software on
May 9th, 2012.
Thanks in advance
--
Kind Regards,
Giuseppe Castagno
Acca Esse http://www.acca-esse.eu
giuseppe.castagno at acca-esse.eu
[1] https://issues.apache.org/ooo/show_bug.cgi?id=125194
[2] http://www.webdav.org/specs/rfc4918.html#locking
[3]
https://wiki.openoffice.org/wiki/Documentation/DevGuide/AppendixC/The_WebDAV_Content_Provider
[4]
http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/ucb/source/ucp/webdav
[5]
http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sfx2/source/doc/docfile.cxx#1023
[6]
http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sfx2/source/doc/docfile.cxx#1065
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
