[OASIS Issue Tracker] Commented: (CMIS-677) Browser Binding URLpatterns

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

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

Gregory Melahn commented on CMIS-677:
-------------------------------------

The conclusion of the discussion in the 22 November call was to not use the objectId in the uri and instead access an object using a path in the uri.  ObjectIds would only be used in url parameters,   So we will not see url patterns like http://example.com/myrepository/0987654321 and will instead see http://example.com/myrepository?objectId=0987654321.   One reason for this decision is the problem that tomcat has with encoding slashes and other special characters (apparently a security issue).   This will restrict the ability of proxies to cache content but we can cover the main use case for caching by having the default response for a document to be a content stream.     Florian will write up a complete list of url patterns for discussion on 6 December. 

> Browser Binding URL patterns
> ----------------------------
>
>                 Key: CMIS-677
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-677
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Browser Binding
>            Reporter: Florian Mueller
>            Assignee: Gregory Melahn
>
> In order to keep browser binding clients as simple as possible we should introduce fixed URL patterns.

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