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 Thu, 02 Aug 2007 07:33:01 GMT
Hi,

I'm not sure if I understand this request for improvement.

> Using datasources

So you suggest to use DataSource.getConnection(..) instead of
DriverManager.getConnection(..)? How do you get / create the
datasource object, using JNDI? What about embedded applications where
JNDI is not available?

> one should be able to rely on the application server to manage PreparedStatement caches

Do you suggest to create a new PreparedStatement for each request?

> therefore pre-creating and holding onto the connection for long periods of time should
not be needed.

Could you explain the advantages of 'not holding onto the connection'?
I know that MySQL closes connections after 8 hours idle time, are
there any other advantages?

> This relates to improvement JCR-313, however, that change did not address the benefits
one could see in using an application server controlled datasource.

What are those benefits?

> Even if jackrabbit does aim to use an embedded database such a system could be configured
to use datasources and

> could benefit from the removal of the synchronization.

In what way would removal of the synchronization be a benefit? Do you
think it would be faster without synchronization? How would you make
sure statements are executed in the right order?

Thanks,
Thomas

Mime
View raw message