db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning P. Schmiedehausen" <...@intermeta.de>
Subject Re: JndiDataSourceFactory
Date Wed, 06 Oct 2004 16:42:16 GMT
Thomas Vandahl <thomas.vandahl@tewisoft.de> writes:

>John McNally wrote:
>> The reason it is not cached is that the DataSource/JNDI concept allows 
>> an adminstration application to change the DataSource that is bound to a 
>> name and an application using that name would automatically start using 
>> a different pool of connections.

>I see. Problem is, that the lookups slow down the application quite 
>badly. Is there anything else one could do?

Use a cache that times out. If you implement a cache that will defer
lookups for 30 seconds or so (configureable!), then you will get the
behaviour that John described after the timeout but still get the
performance gains from having a cache.

There is an implementation of such a time-out cache in the Turbine
code base.


Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

"Fighting for one's political stand is an honorable action, but re-
 fusing to acknowledge that there might be weaknesses in one's
 position - in order to identify them so that they can be remedied -
 is a large enough problem with the Open Source movement that it
 deserves to be on this list of the top five problems."
                       -- Michelle Levesque, "Fundamental Issues with
                                    Open Source Software Development"

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message