All operations that create, modify or delete objects or change the state of the repository in any way use HTTP POST. Since this binding is optimized for use in browser applications, the format of the transferred data is aligned to the capabilities of HTML forms and described in this specification in HTML terms. See section 1.4.4 for a description of how HTML forms are used for CMIS operations
Write Operations Summary Table
The following table defines the POST request responses:
If a ‘file’ control is included in the form, the content stream of the object MAY be updated with the content of the file in the same operation.
moveObject
201
JSON representation of the moved object
yes
yes
deleteObject
204
Empty
no
yes
deleteTree
204
Empty
no
yes
When the operation partially succeeds, meaning that a 204 is returned but some objects in the tree are not deleted, an instance of type http://docs.oasis-open.org/ns/cmis/browser/201103/ids containing a list of id’s of the objects not deleted SHALL be returned.
setContentStream
201
JSON representation of the object
yes
yes
deleteContentStream
204
Empty
no
yes
Multi-filing Service
addObjectToFolder
201
JSON representation of the added object
yes
yes
removeObjectFromFolder
201
JSON representation of the removed object
yes
yes
Discovery Service
query
200
Query results
no
no
Versioning Service
checkOut
201
JSON representation of the PWC
yes
yes
cancelCheckOut
204
Empty
no
yes
checkIn
201
JSON representation of the checked-in object
yes
yes
Policy Service
applyPolicy
200
JSON representation of the updated object
no
yes
removePolicy
200
JSON representation of the updated object
no
yes
ACL Service
applyACL
200
JSON representation of the new ACL
no
yes
Operations Summary Table
The following table assigns “selector” and “action” values to CMIS operations:
