[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-135) createDocument &checkIn - Accept an optional contentStream input. How is this included andencoded?
[ http://tools.oasis-open.org/issues/browse/CMIS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10231#action_10231 ]
Al Brown commented on CMIS-135:
-------------------------------
History - some repositories do not support long creates or checkins. Ie, create must have everything. Same with checkin. I know DCTM does not allow updates to PWC. So this is a compromise to support both models.
In the REST binding, on create or checkin, the content can be specified in the atom entry content element either as part of the src attribute or contained in that tag. We should support that model since that is how APP functions
> createDocument & checkIn - Accept an optional contentStream input. How is this included and encoded?
> ----------------------------------------------------------------------------------------------------
>
> Key: CMIS-135
> URL: http://tools.oasis-open.org/issues/browse/CMIS-135
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: Domain Model, REST/AtomPub Binding
> Affects Versions: Draft 0.6
> Reporter: Ryan McVeigh
> Assignee: Ethan Gur-esh
> Priority: Critical
>
> Sections: 3.4.1 & 3.7.3
> 1) Is this really necessary, as there is an entire set of stream services?
> 2) The schema (CMIS-Core) includes a type (cmisContentStreamType) but it is not referenced anywhere else except in CMIS-Messaging (which appears to be SOAP-related). How might this stream be incorporated into an Atom Entry (for REST) - is it Multi-Part?
> 3) It seems reasonable that a stream be provided to aid in atomic creates/updates.
> 4) If streams really are expected to be large enough to merit a sub-range requirement on getContentStream (see 3.4.7), then is it realistic to expect that one would base64 encode such a beast?
> 5) If the Entry document schema is modified to accept an encoded stream (or the spec clarified as to where this is placed within the Entry), then why would that stream also not be available from getProperties? This leads to an asymmetrical usage of streams.
> 6) For large streams where encoding is not practical, there should be a way to (for example) create a document which requires a stream, set that stream in a separate operation, and then commit/checkin that change (at which time the "required stream" is enforced).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]