Re: [cmis] thinClientURI discussion

["Huebel, Jens" <j.huebel@sap.com>]

Would it help to define an additional parameter in this case that can be appended to the URL and filled by the application? Something like &userContext=blessedUI? Something not interpreted by CMIS just passed through? Could also be done via CMIS extensions.

jens

From: Peter Monks <pmonks@alfresco.com>
Date: Wednesday 29 January 2014 00:43
To: Jay Brown <jay.brown@us.ibm.com>, "Mueller, Florian" <florian.mueller02@sap.com>
Cc: "cmis@lists.oasis-open.org" <cmis@lists.oasis-open.org>
Subject: Re: [cmis] thinClientURI discussion

I've fielded this request several times in my work supporting Alfresco integrators.  The general requirement is for the ability for the client app (usually a web app) to be able to reliably "link through" to the Alfresco UI, without having to bake in a bunch of hardcoded, repository-specific, probably version-dependent URL construction logic.

One possible wrinkle is that there isn't necessarily a single UI for the server to redirect the client to.  Alfresco (for example) provides 3 different UIs, and is integrated with several 3rd party UIs that customers may be using exclusively (and therefore may want returned from calls such as this one).  I guess this could be a configurable thing on the server side though i.e. the customer has to pick a "preferred" or "blessed" UI, and that's the single one that would be redirected to via this mechanism.

Cheers,
Peter

On Jan 28, 2014, at 3:19 PM, Jay Brown <jay.brown@us.ibm.com> wrote:

I agree this would be a clean way to do it, but I don't have a use case for this here.  

Perhaps someone else will...


Jay Brown
Senior Engineer, ECM Development
IBM Software Group
jay.brown@us.ibm.com

<graycol.gif>"Mr. Florian Mueller" ---01/28/2014 09:18:54 AM---Hi, In our last call we discussed (and finally rejected) the idea of a thinClientURI that can direct

<ecblank.gif> From:	<ecblank.gif> "Mr. Florian Mueller" <florian.mueller02@sap.com>
<ecblank.gif> To:	<ecblank.gif> cmis@lists.oasis-open.org,
<ecblank.gif> Date:	<ecblank.gif> 01/28/2014 09:18 AM
<ecblank.gif> Subject:	<ecblank.gif> [cmis] thinClientURI discussion
<ecblank.gif> Sent by:	<ecblank.gif> <cmis@lists.oasis-open.org>

---

Hi,

In our last call we discussed (and finally rejected) the idea of a thinClientURI that can directly access the native repository web interface for folders and documents.
Today, I had an idea how this could be done in a very lightweight fashion with (and only) the browser binding.

Browser binding object URLs have a cmisselector parameter. We could introduce a new value for that, for example „native“. It either returns the HTTP status code 307 (Temporary Redirect) with a Location header pointing to the native web interface for this object or the HTTP status code 404 (Not Found) if the repository doesn’t have a web interface or doesn’t want to provide this feature. How the redirect URL is composed is repository specific and could depend, for example, on the object type and on the property values of the object.

Do you think this idea is worth pursuing?


Regards,

Florian