From: Dannes W. <da...@ex...> - 2011-05-14 11:59:10
|
Casey, I have no clue anymore what you are trying to attempt; the mail thread is getting diffuse; On 14 May 2011, at 0:58 , Casey Jordan wrote: > Unfortunately, I was forced to switch to the old eXist WebDAV implementation in (controller-config.xml), because with the Milton servlet I got the same failure as in your mail once (Actually except for several tests, I have always used only the the old implementation) I really like to suggest NOT to use the old implementation. There are well known issues, I think we'll remove it from trunk in the future... > So does that mean that regardless of what version control system you use through webDAV this "trailing zero's" problem is apparent? and > > otherwise you occasionally will commit trailing zeroes (to 4K boundary) - this is complication by design. Anyway, I have been thinking of the "trailing zeros to 4 kay" thing; My conclusion is that it is a problem with your webdav client; Internally eXist-db does NOT know the exact size of an XML document. Why? Because the size of the serialized XML document depends on many factors, like indent settings, line-ends yes/no etc. To provide an *indication* on the document size, we check the number of pages (default 4 kbyte). The size reported is number of pages times 4 kbytes. This is a fundamental design thing, there is no real reliable alternative for this. We'll always endup in a guesstimate Some webDav clients are programmed in a 'crappy' way. They trust on the document size reported e.g. by the PROPFIND method, instead of retrieving the (chunked) byte stream from the server until the byte stream ends. As a result your client writes the modulus-4k file to your disk. Fortunately many clients are robust for the way eXist-db reports the approximate filesize....... Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |