Andrea Aime wrote: > Jody Garnett ha scritto: >> Thanks Andrea! That was a great overview of the trade-offs. >> >> I am looking at how we do connection pools in GeoTools - but more >> towards JNDI lookup then >> handling of prepared statements. Is there anything you would like me >> to look out for when >> I do this work? > Yeah. Not everybody is using JNDI, so please leave the door open for > manually configured pools where JNDI is not available. > I would really like to see some kind of pluggable API allowing the > usage of DBCP, C3PO and the like, JNDI being a player like the others. > And have a default pooling too, maybe based on DBCP. Well the idea is what I had in mind - but I confess that I have not recognized half the acronyms you have just mentioned. I will make a proposal for you to tear to shreds ( ie. constructive feedback) shortly. >> It sounds from your email that a shared connection pool in a J2EE >> setting (ie shared with >> other web applications) may result in a glut of cached prepared >> statements? > Yeah, it would. It's usually best to configure one connection pool > for application. That's what I've seen in production environments > around here, each app is given a small but private connection pool, > usually around 10 connections. > If you have a shared one, the most active app using prepared statement > will rule the pool (ps wise). Ah the fine balance of control; it is hard to give it up .. but I suppose that is what this JNDI lookup is all about. Jody
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
