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=34457#action_34457 ] 

Florian Müller commented on CMIS-758:
-------------------------------------

Here is an alternative, more extensive proposal: Introduce something similar to stored procedures.

The CMIS server provides a scripting environment (e.g. JavaScript), which provides an API with all CMIS operations. 
Clients trigger a script on the server and provide (free form) metadata and content. The script processes the data on the server and returns (free form) metadata and content. The API may provide operations to control transactions (start, commit, rollback).

Discussion items:
- How can scripts be deployed? Can only an administrator do that? Is there an extra interface? Are scripts just documents of a special type and/or in a special location?
- How is the metadata and content be transferred? (Example: multipart message, the first part contains a free form JSON object, subsequent parts contain content.)


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