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

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

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

Ken Baclawski commented on CMIS-758:
------------------------------------

The asynchronous processing part of the proposal is similar to the one discussed by CMIS4DAM.  The main use of asynchronous processing for DAM would be for dynamic rendition since creating a new rendition can be time-consuming.  Given this use case, I suggest that asynchronous processing be an independent feature that could potentially be applied to other operations.  Here is the proposal:
https://www.oasis-open.org/apps/org/workgroup/cmis4dam/download.php/56932/dynamicRenditionAndAsynchronous.docx

The main concern about this feature for CMIS4DAM was the status monitor object.  Some TC members felt that it would not be easy for a repository to support such an object, and preferred another approach to asynchronous processing that did not involve creating a new object.

> Discussion of more powerful batch operations for next version
> -------------------------------------------------------------
>
>                 Key: CMIS-758
>                 URL: https://issues.oasis-open.org/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 was sent by Atlassian JIRA
(v6.2.2#6258)