[OASIS Issue Tracker] Commented: (CMIS-264) Streaming handling forFolder Children Collection POST needs clarification.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279#action_17279 ] 

Al Brown commented on CMIS-264:
-------------------------------

JIRA Cleanup

> Streaming handling for Folder Children Collection POST needs clarification.
> ---------------------------------------------------------------------------
>
>                 Key: CMIS-264
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-264
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Al Brown
>            Priority: Minor
>             Fix For: Draft 0.62
>
>
> 540-545 - would be clearer merged into one paragraph because the "part of the atom entry" @544 is actually what you need to do when the stream is required by the type (as @540). You can't do edit-media (@545) when the stream is required.
>       First, stream is no longer a valid link.
>       Second, on edit-media: If you are POSTing to create a document and the stream is required, then it must all come in a single request, the properties and the stream. To use edit-media, you would POST the properties, then fetch the properties from the location header, and find the edit-media link. Then you'd PUT to the edit-media resource to create the stream. However, there is nothing that guarantees that you'd ever follow through on the edit-media PUT, and the document (in this case) requires a stream (i.e. can't be created without one). So the only choices are:
>           o Create a document in a checked-out form, and ensure that a stream is created at some time before check-in. Some repos may not be able to do this, and this interaction model is not described anywhere in Part I or II.
>           o Require the repo to create an appropriate "dummy" stream. It may not be possible to do this for all document types, and some repos may not be able to handle this. Also, this interaction model is not described in Part I or II.
>           o Require the stream as a part of the createDocument service invocation (POST to folder collection). This is what is described in Part I. The only two ways I am aware of to satisfy this for POST is to base64 encode the stream as part of the Entry's content element, or somehow do a multi-part POST (but I haven't looked into AtomPub to see if this is ok).
>           o I guess the other way to do this would be to create a new resource for pre-creating content stream data - PUT to this and get back a (temp) identifier that could be referenced by the POST to createDocument. But this is entirely new.

-- 
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