In general I agree, but the reality is that most CMIS clients don't support cookies and even if you use the OpenCMIS client you have to consciously turn it on. Therefore a server has to be prepared to fallback back to something else. And this something else is probably repository specific.
Florian ----- Original Message ----- From: "Florent Guillaume" <[email protected]> To: [email protected] Cc: "Achim Weigel" <[email protected]> Sent: Monday, October 17, 2011 6:53:20 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: Stable session id for a OpenCMIS server when using OpenCmis Workbench I would be for encouraging client writers to use cookie support, it's really the best way, cookies are designed to allow a server to maintain sessions when using HTTP. Anything else will be artificially constrained IMHO. Florent On Mon, Oct 17, 2011 at 12:40 PM, Florian Müller <[email protected]> wrote: > Hi Achim, > > This has actually nothing to do with OpenCMIS. > I assume your servlet engine sets a cookie to maintain the session. Since > most CMIS client don't send that cookie back, each request looks like a new > session and the servlet engine generates a new id. > You could, of course, turn the cookie support in the OpenCMIS client on, but > don't expect that other clients have that capability. > > CMIS is stateless. Applying state on the server side is rather difficult. > Your only hint is probably the username or maybe the combination of the > username and the IP address. > > > Florian > > > On 17/10/2011 09:38, Weigel, Achim wrote: >> Perhaps I should add that we are doing this in the method >> getCallContextMap(HttpServletRequest request) of our CallContextHandler. >> >> -----Original Message----- >> From: Weigel, Achim [mailto:[email protected]] >> Sent: Montag, 17. Oktober 2011 10:29 >> To: [email protected] >> Subject: Stable session id for a OpenCMIS server when using OpenCmis >> Workbench >> >> Hello, >> >> we are implementing an (Open)CMIS compliant server and need some kind of >> session concept for it. We are using the OpenCMIS Workench as client and >> tried out the following using the atompub binding: >> >> We implemented and configured a CallContextHandler and tried to fetch the >> session id from the request: >> >> String sessionId = request.getSession().getId(); >> >> Unfortunately the id is different for all requests. >> >> Do you perhaps know how we could resolve this? >> >> Thank you very much in advance and best regards, >> >> Achim >> > > -- 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
