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-763) Discussion - Should CMIS 1.2 features only be defined for the browser binding?

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

Florian Müller commented on CMIS-763:

I've implemented all bindings, on the client (Java + .Net) and on the server (Java) side. 

The WS binding is the hardest to get right. All WS frameworks I've seen have one or more issues with attached content (memory, performance, security, etc.). That's handable with some effort and special code for each runtime environment and WS framework, if there is only one document attached to a call. It gets much harder to impossible if we attach more than one document to a call, which we are discussing with the batching support.
The WS binding is also much slower than the other binding. In real life the other binding should be recommended. The WS binding is the last resort.
From a technical perspective, deprecating the WS binding seems to be a good idea. At least, it should not be required for a CMIS compliant server.

The AtomPub binding lacks some features and it depends on the application if that matters or not. Some things could be fixed in the next version of the spec, but some are Atom constraints and we cannot do much about it.
Because the AtomPub binding is widely supported, I would add new features to it if possible, but focus in the Browser binding.

> Discussion - Should CMIS 1.2 features only be defined for the browser binding?
> ------------------------------------------------------------------------------
>                 Key: CMIS-763
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-763
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Task
>          Components: Browser Binding
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
> Please discuss here  as to whether we should stop adding new features to the AtomPub and WS bindings for all versions > 1.1. 
> E.g. All new features will be supported in the Browser Binding only if yes. 

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]