chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florent Guillaume ...@nuxeo.com>
Subject Re: OpenCMIS and CMIS 1.1
Date Sat, 27 Oct 2012 14:41:11 GMT
Agreed, the right path is to have a single library support both versions.
As Jay is saying, even at the cost of significant extra development.

Florent

On Fri, Oct 26, 2012 at 11:31 PM, Jay Brown <jay.brown@us.ibm.com> wrote:

> I would strongly recommend having the latest version of OpenCMIS always
> support current and back versions of the specification.   Even at the cost
> of significant extra development.
>
> Since OpenCMIS is now effectively the standard client library, having to
> use a different version to take advantage of > 1.0 versions may have the
> effect of slowing adoption or worse creating a implied/perceived
>  compatibility gap between providers who move up and those that take longer
> to adopt 1.1.
>
>
> Jay Brown
> Senior Engineer, ECM Development
> IBM Software Group
> jay.brown@us.ibm.com
>
> [image: Inactive hide details for Florian Müller ---10/26/2012 02:07:08
> PM--- Hi, The CMIS 1.1 specification is now stable. The public]Florian
> Müller ---10/26/2012 02:07:08 PM--- Hi,  The CMIS 1.1 specification is now
> stable. The public review ended about
>
>
>
>    From:
>
>
> Florian Müller <fmui@apache.org>
>
>    To:
>
>
> <dev@chemistry.apache.org>,
>
>    Date:
>
>
> 10/26/2012 02:07 PM
>
>    Subject:
>
>
> OpenCMIS and CMIS 1.1
> ------------------------------
>
>
>
>  Hi,
>
> The CMIS 1.1 specification is now stable. The public review ended about
> two weeks ago. That is, nothing material can be changed anymore.
>
> OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete the
> CMIS 1.1 support, we would have to add a few new operations and
> constants.
>
> My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
> library and the same server framework. The client should automatically
> adapt to the CMIS version of the repository. The server framework should
> be able provide endpoints for both CMIS versions.
>
> The alternative is to provide separate libraries for each CMIS version.
> That would make the internal implementation simpler, but I think that
> would be more cumbersome for OpenCMIS users.
>
> Any thoughts?
>
>
> Thanks,
>
> Florian
>
>
>
>


-- 
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message