The browser binding discussion is pretty new. If this binding will be required or optional hasn't been decided yet.
We could build a proxy but the performance would suffer. There would be two network connections and a lot of data conversion necessary. That's fine for a prototype but probably not for a productive system. Also, the AtomPub binding does not support the complete CMIS spec. A proxy would inherit this deficits and that isn't necessary. - Florian -----Original Message----- From: Richard McKnight [mailto:[email protected]] Sent: Dienstag, 29. Juni 2010 17:09 To: [email protected] Subject: Re: CMIS Browser Binding +1 On this .... a couple of questions. * Would this be a required or optional binding * Should we develop a proxy (as part of chemistry, that can be wrapped around a CMIS-REST repository to provide a browser binding? Rich Florian Müller wrote: > Hi, > > There is currently a discussion starting in the CMIS Technical Committee to > add a third binding called "browser binding". The idea is to provide the CMIS > data in a way that it is easily consumable in a web browser. This time, the > design of this binding should be accompanied by an implementation to make > sure that the design actually works. > > I have played a bit. I've implemented a stub for such a binding as an > extension of the OpenCMIS server framework. At the moment it exposes the > repository infos, type definitions, CMIS objects and folder children in a > JSON format, which follows the CMIS XML schema. That's probably not the > structure we will end up with, but it's a starting point. It bundles to > InMemory repository for testing. > The implementation is pretty light-weight. It just consist of 4 short > classes. Most of the infrastructure is already in OpenCMIS. > > I would like to open a sandbox project in Chemistry for this, parallel to > OpenCMIS. It would depend on OpenCMIS but would not interfere with OpenCMIS. > > WDYT? > > > Cheers, > > Florian > -- *Rich McKnight* Technical Consultant Alfresco Software, Inc. [email protected] 512-692-6179 Blog: http://oldschooltechie.com
