Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <422623F7.6080400@apache.org>
Date: Wed, 02 Mar 2005 21:37:11 +0100
From: Sylvain Wallez <sylvain@apache.org>
Organization: Anyware Technologies
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: jackrabbit-dev@incubator.apache.org
Subject: Re: Lifetime of a session?
References: <4225DDEA.9090609@apache.org>
 <f2fbc46df58915939b85ff4158c6a82b@mac.com>
In-Reply-To: <f2fbc46df58915939b85ff4158c6a82b@mac.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Suhail M. Ahmed wrote:

> Hi Sylvain,
>
> The Session object is returned on performing a login on the 
> repository. Looking at RepositoryIml you will see
>
>  Session ses = new XASessionImpl(this, lc, wspInfo.getConfig());
>  activeSessions.put(ses, ses);
>
> You should I think couple the repository session life cycle to your 
> http session life cycle. I haven't dug deeper in to the object graph 
> derived from session so I can't say anything about the thread safety 
> of Item and its sub classes. I do see some nifty synchronization in 
> the content store implementation so I would think that at that level 
> things are thread safe. I think the optimum route is to use a session 
> listener to login and logout from the repository.


That was my opinion also, but the thread-safety on session itself may be 
a concern if a single user issues several request simultaneously. How 
will the transaction manager behave in such circumstances?

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }