← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (CMIS-78) setContentStream shouldinclude an optional changeToken as an input

From
OASIS Issues Tracker <>
Date
2009-04-14T16:36:30+00:00
ID
474396569.1239726990365.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Commented: (CMIS-78) setContentStream shouldinclude an optional changeToken as an input
[ http://tools.oasis-open.org/issues/browse/CMIS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10172#action_10172 ] 

Al Brown commented on CMIS-78:
------------------------------

I am okay with this if there is a repository info capability that specifies if change tokens are specified

> setContentStream should include an optional changeToken as an input
> -------------------------------------------------------------------
>
>                 Key: CMIS-78
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-78
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.50
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>             Fix For: Draft 0.6
>
>
> Currently, the "updateProperties" method for a document takes a changeToken as optional input (so that the repository can perform optimistic locking/updating.)
> But setContentStream doesn't. 

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →