On 9/22/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 9/21/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
> There is still some not yet answered question about JCR Session usage:
> can it be used as a long-live object and shared between different
> threads? Is it dangerous to do so?
Yes. JCR sessions are not thread-safe so you should not try to use one
concurrently from multiple threads. If you want, you can use a
session-pool from which you borrow a sessions whenever one is needed
to avoid the session startup cost and to keep caches loaded.
Thanks Yukka. That's what I have thought too, but I was looking more
for technical arguments, so that I understand the real risk. Or at
least a pointer to where to look for possible problems.
I mean, if the access through the shared Session is read-only, what
can go wrong? Have a node/property loaded 2 times? That's not so
bad/risky (at least at first glance :-) ).
BR,
./alex
--
.w( the_mindstorm )p.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development
