Re: [Exist-development] ANN: upgrade of webdav interface in Trunk

[Dannes W. <da...@ex...>]

Anton,

thank you for your testing and deedback!

On 25 Sep 2010, at 18:01 , Anton Kolev wrote:

> davfs2 1.4.5, Authorization: Basic
> 
>    Read    Cr/Wr   Delete  Ren/move
> Col OK(1)   OK      OK      OK
> Bin OK      (2)     OK      OK
> XML (3)     (2)     OK      OK
> 
> (1): Names with intervals becomes ...%20...
> (2): Lock exception
> (3): Wrong Content-Length: x*4k, Old implementation works because of using Transfer-Encoding: chunked, without Content-Length

I have seen these (1) as well, although the webdav framework should shield us from these issues. Probably we have a double encoding thing somewhere....

(2) I'll dive into it myself. It is impossible in exist to get a lock on collection. I implemented it by using a null reference, but that does not work as it seems. I have some ideas how to improve this

about (3) yes, for XML documents we have no workaround for that; basically we cannot tell the exact size of an xml document, because in the database....... there are no documents, just a set of nodes. The size of the document, when retrieved from the database' depends on a few factors, e.g. serialization parameters used to covert the nodes to a document.

The size you see in the Java client, Html interface, Rest interface and also webdav is an guestimation, to get an indication of the size of the document (bytes, kbytes, megabyte, gigabytes). Basically it is the 'internal page size', which  is by default mod 4kbytes.

Does the size affect the correct operation of the client? I really don't hope, because I cannot think of a good solution.


Kind regards

Dannes

--
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624