jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Moseley <...@osafoundation.org>
Subject Re: DP Persistence manager implementation
Date Thu, 02 Feb 2006 16:40:17 GMT
On 2/2/06, Marcel Reutegger <marcel.reutegger@gmx.net> wrote:

> IMO the purpose of the SimpleDbPersistenceManager is mainly embedded
> databases where a connection failure is highly unlikely, as there is no
> network in between.

there seems to be a lot of fuss about SDPM being "simple" or mainly
for embedded use, but an increasing number of people seem to want to
use jackrabbit against network dbs with connection pools. so let's
give them what they want.

how about renaming SDPM (since "simple" is a vague, non-descriptive
term)  to EmbeddedDbPM and providing GenericNetworkDbPM. what would
this new class do that's different from SDPM, other than using JNDI to
look up its connection? i'm not a PM expert, but i have looked over
SDPM a few times, and i don't remember anything else that would need
to change, except maybe the closing of the connection at the end of
the PM's lifecycle.

> If concurrent write performance should become a real issue that's where
> we first have to deal with it.

i can't quantify it yet, but there is some intuition that points to
this being the bottleneck in running cosmo under heavy load (hundreds
of simultaneous webdav requests).

View raw message