chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller <>
Subject Re: No Content Stream vs. Empty Content Stream
Date Fri, 09 Mar 2018 10:08:39 GMT
Hi Jake,

The Chemistry dev list is the right place to ask.

CMIS makes a clear distinction between "no content" and "content with 0 
bytes". On a file system, there is no difference between the two. When a 
document is created, an empty file is created. The information if there 
was no content stream or an empty content stream is lost. When 
getContentStream() is called, the FileShare server has to make a choice, 
which can be wrong.
Please note, that the FileShare implementation is a very naïve 
implementation and its main purpose is to provide some sample code. In a 
productive implementation, you would record whether there was a content 
stream or not and based on that return an error or an empty content.

- Florian

> Hello,
> I'm looking to better understand how to handle the difference between a
> cmis:document having no content stream, and a content stream that is 
> empty
> (0 bytes). This scenario is handled differently by the example CMIS
> servers, and I'd like to understand which is correct.
> The example in-memory server tracks a document's content by
> maintaining a ContentStream
> (fContent
> <>
> ) for each Document. If the document has no content stream, then 
> fContent
> is null. If the document has a content stream, fContent is a
> ContentStreamDataImpl
> <>
> object
> which may have 0 or more bytes of underlying data. Whether fContent is 
> null
> or is a populated ContentStream object, it is returned by the
> getContentStream service.
> The in-memory server handles no content stream differently than an 
> empty
> content stream. This matches the TCK test testAppendStream
> <>
> which starts by creating a document with empty content. The test 
> ensures
> that a non-null ContentStream is returned after the document is 
> created,
> and that ContentStream must be empty (0 bytes).
> The fileshare example server does not differentiate between no content
> stream and a file having 0 bytes of content. In its getContentStream
> implementation
> <>,
> it throws a CmisConstraintException if the file has 0 bytes (per the
> specification
> <>).
> This causes the testAppendStream to fail, because it expects an empty
> content stream. If the getContentStream service returned an empty
> ContentStream instead, this would cause the CreateDocumentWithNoContent
> <>
> test to fail, because the browser binding will add a filename "content"
> <>
> if the returned ContentStream has no filename set.
> So I'm not really sure where the problem lies. If we consider that the
> in-memory server's functionality is correct, then the fileshare server
> should have CapabilityContentStreamUpdates.NONE. The fileshare server 
> can't
> know if a file has 0 bytes or no content stream. If this distinction 
> isn't
> important, then tests shouldn't enforce this difference. Also, the 
> behavior
> of the browser binding is different than other bindings, but I don't 
> know
> if that's an issue.
> Please let me know what you think. I'd be happy to help with code 
> changes
> (if needed). Also please let me know if there is a more effective way 
> to
> communicate this information because this is my first time using the 
> Apache
> dev mailing lists.
> Thanks,
> Jake Karnes
> ECM Consultant
> Zia Consulting
> m: 408.314.7075
> 5525 Central Avenue, Suite 200
> Boulder, CO 80301

View raw message