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=35123#action_35123 ] 

Jay Brown commented on CMIS-758:

More thoughts on this. 
How about something like this for the forward id mechanism?  
Note: If we added this I would prefer it be mandatory.   
I don't want this feature to be optional or be filled with optional syntax. 

Batching proposal - forward ids:
For every (updating) batch item an implied variable will exist
    batch:<batch operation position>  (e.g. batch:9 )
that will stand for the id of the resulting object from the operation.  
(So there is no additional work to declare them) 
This variable can then be used in place of a cmis ID later in the batch.

Example of a 3 item updating batch that uses this feature: 
  [0] - create document (details...) 
  [1] - create folder (details) 
  [2] - FileDocInFolder (docid=<batch:0> folderid=<id=batch:1>)

Note that batch:2 would be the id of the same folder returned by [1] if it were to be referenced later in the batch. 

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