Paco, as you probably know by now, jcr Sessions are not thread safe, and so exposing them in a multi-thread environment may become a risk for the data. I am not sure how your application is behaving and how do you protect against thread contention at the session level, so it is kind of hard to give an advise. What I can share is the fact that in a read-only mode you can probably share a session between different threads.
./alex -- .w( the_mindstorm )p. On Nov 21, 2007 6:15 PM, Paco Avila <[EMAIL PROTECTED]> wrote: > Hi > > Our application using Jackrabbit is an Document Management System > (OpenKM). Actually we prevent an user log into the web aplication twice, > so there is only one Jackrabbit Session per web user. > > But we also expose several methods via WebServices and here is the > problem: if an user is logged into the web application, the same user > can't user WebService API because he is already logged into the system. > > I have think two options: > > - Reuse an existing Jackrabbit Session for both web user and the same > ws api user. PROBLEM: is it a good practice for Jackrabbit? > > - The web user hace one JR Session and the ws api user have another > session. PROBLEM: Every web user need another WS user and this can be > hard to manage because we need to set permissions for both users and > should be the same permissions for them. > > Any tip? > > > -- > GIT CONSULTORS > > www.git.es > > Tel: +34 971 498 310 > Fax: +34 971 496 189 > > C/ Francesc Rover, 2B. > 07003 Palma de Mallorca – Illes Balears (España) > > >
