Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: pass (athena.apache.org: domain of j.huebel@sap.com designates
 155.56.66.96 as permitted sender)
From: "Huebel, Jens" <j.huebel@sap.com>
To: "dev@chemistry.apache.org" <dev@chemistry.apache.org>,
	=?Windows-1252?Q?Florian_M=FCller?= <fmui@apache.org>
Date: Fri, 11 May 2012 12:40:54 +0200
Subject: Re: CMIS Bridge
Thread-Topic: CMIS Bridge
Thread-Index: Ac0vYotsaV0urHVKTtKVKoFiTKZ/3Q==
Message-ID: <CBD2B937.2D7%j.huebel@sap.com>
In-Reply-To: 
 <a5da8d74ef52421398a4e944b3e843a2-EhVcXl9JQQFXRwQFDQkEXR0wfgZLV15fQUBFBEFYXS9ZUF0WWlloB11LX15YLkQBXFxeQ1pTUQo=-webmailer2@server05.webmailer.hosteurope.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.1.120420
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I think this would be a very useful tool in out project=8A

+1

Jens


On 11.05.12 12:38, "Florian M=FCller" <fmui@apache.org> wrote:

> Hi all,
>
> We have built something that we would like to contribute to OpenCMIS.
> We have called it the CMIS Bridge.
>
> The CMIS Bridge acts like a proxy between a CMIS client and a CMIS
> repository. This proxy can intercept CMIS requests and manipulate the
> data that goes in and out.
>
> Here are a few use cases for the CMIS Bridge:
> - Binding changes. For example, a repository with a broken Web Services
> binding implementation can use the bridge to accept Web Services calls
> and turn them into AtomPub calls. And vice versa, of course.
> - Repositories that don't implement the browser binding yet can use it
> as a quick way to provide the browser binding.
> - The bridge can also host a web application that uses the browser
> binding without the hassle of dealing with the same-origin policy in web
> browsers.
> - It can be used as a repository filter. It may only allow access to a
> few but not all repositories that a server exposes.
> - The bridge may handle authentication mechanisms that the target
> repository cannot handle. The combination of the browser binding and
> OAuth comes to mind.
> - Objects and properties can be hidden and virtual objects and
> properties can be added on the fly.
> - Objects can be enriched on the fly. For example, when a client
> uploads a MP3 file the bridge can extract the MP3 metadata and adds them
> before the object is created on the target repository.
> - Folder structures and templates can be created on the fly.
> - It can be used in protect a repository. For example, the repository
> could run behind a firewall and the bridge resides in the DMZ.
>
> There are probably many more use cases.
>
>
> The current implementation is quite basic. It works, but there is a lot
> of room for improvement and optimization. This is something we want to
> do over the next weeks and months.
>
> Are there any objections to add this to OpenCMIS?
>
>
> Thanks,
>
> Florian
>