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-736) Remove ETAG recommendation from AtomPub section


    [ http://tools.oasis-open.org/issues/browse/CMIS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29282#action_29282 ] 

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

Entity Tags work well for more or less static content and may work for CMIS document content.

But in order to generate an Entity Tag for, let's say, a document entry you have to consider the state of the document, the state of a potential PWC and other documents in the version series, the query parameters, the user and the users permissions at this point in time. 

Gathering all this data and managing the ETAGs is more expensive than providing a fresh Atom entry. It is also pretty error-prone. I tried to implement it and gave up eventually. I cannot recommend trying it.

It also doesn't make much sense on the client side. It's more efficient to work with the change token or the last modification date than to keep an extra piece of (binding specific) data.
An ETAG doesn't reflect the state of the object. It represents the object AND all it's dependencies, which is usually not very interesting for a client.


> Remove ETAG recommendation from AtomPub section
> -----------------------------------------------
>
>                 Key: CMIS-736
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-736
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: REST/AtomPub Binding
>    Affects Versions: V1.1
>            Reporter: Florian Müller
>
> CMIS 1.0 recommends the support of ETAGs (section "3.2.1 Entity Tag"). The implementation in the context of CMIS is rather difficult and in some cases impossible. Since ETAGs are not supported by many CMIS repositories today and almost no CMIS client takes advantage of them, I would like to remove them from CMIS 1.1.

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