jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller" <thomas.tom.muel...@gmail.com>
Subject Re: [jira] Created: (JCR-1050) Remove synchronization from JNDI data sources
Date Fri, 17 Aug 2007 05:45:15 GMT

Currently Jackrabbit uses one persistence manager per workspace, and
one for versioning. That means the same persistence manager is used
for all sessions (in a workspace).

> there should be a new manager per session, ie per usage thread.

While the current architecture has advantages, the approach 'one
database connection per session' also has advantages. I don't think it
will be easy to implement, and there would be additional problems
(transaction isolation for example).

We should try to find out how much faster / more scalable this
solution would be. What about defining a use cases and then writing a
small 'benchmark type' application? To find out if using multiple
connections really would help, and how much it would help. Test driven

What do you think?

View raw message