OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-758) Discussion of more powerful batch operations for next version

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

Jay Brown commented on CMIS-758:

How to support setContentStream in the batch request.  

Currently we have two options:
1.  Multipart posts so the binary portion can stay binary over transport. 
2.  Base64 encoding of the content inside of the document's metadata (JSON or XML)  (like we support today for a createDocument ) 

Argument for #1 so far has been that it is more efficient over the wire than #2 and requires less processing. 
I did an informal test where I took a 1.5 MB jpg and base64 encoded it; then did gzip header compression on it.   This is effectively what would be happening in the #2 scenario. 
Then I took the same file and just ran it through the gz header compression.   (as would happen typically with #1) 
Result was that both were roughly equivalent in size.   So I would suggest that size over the wire for #1 and #2 is [ O() ] equivalent when gz compression is turned on which should be the case most of the time.  

Now I am leaning toward just supporting  #2 due to the ease of implementation for clients and general simplicity  (easier to clearly define using a technique already used in the spec)  I am concerned about interoperability issues if we required multipart for this. 
This leaves the question of what about those cases where the document is an extremely large document. (e.g. multi gigabyte video file, etc.)  I would argue that these types of documents are not in the target use case for batch update where a client is creating thousands of objects in a single request.    E.g. if you wanted to create 1000 of these files it would still be wise to batch create them (sans content ) in one request,  then do a setContentStream for each. 

> Discussion of more powerful batch operations for next version
> -------------------------------------------------------------
>                 Key: CMIS-758
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-758
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
> Creating this record as a placeholder for discussions on this subject. 
> What additional batch features should we support in v.next? (e.g.  batch Create, Delete, ...) 
> What should they look like? etc. 
> Please comment.

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]