Re: [Eledge-developers] RE: Eledge-developers digest, improving scalability

[Robert Z. <ro...@sc...>]

Chuck Wight wrote:

>I agree that we need to find a way to make Eledge more scalable.  Going to
>Struts + Velocity is probably a good idea, but Robert and Richard know much
>more about this technical end than I.  One of the simple things that we can
>do is to use existing resources more efficiently.  For example, when I
>originally created some of the servlets I did not fully understand issues of
>JDBC Connections, Statements and ResultSets, so I created many more
>Connection objects than was really required.  We can economize on this by
>reusing Connection objects, and we can utilize Connection pools.  Mainly,
>this requires setting up some parameters in Tomcat, and going through the
>code to make certain that every Connection object is explicitly closed()
>when it is no longer needed by the user (and is therefore freed to the pool
>for other users).  I understand that relying on the Java garbage collector
>to do this is not sufficient.
>
>Chuck
>  
>

Definitely true. I've slowly been going through as I rework, debug, add 
features, etc. and have been trying
to explicitly close result sets, statements, and connections. Regarding 
pooling, that is also very true.
There are a variety of "connection pooling" packages out there (several 
from jakarta.apache.org of varying degrees
of sophistication, as well as other packages from other sources). I 
haven't determined which will be best to incorporate into eledge,
but, it's definitely something we want to keep in mind and work into 
eledge during our refactoring.

Robert