Changes between Version 2 and Version 3 of DatabaseConnectionsForThreadsAndNewPool

Timestamp:

Jan 31, 2011, 11:14:47 PM (13 years ago)

Author:

simonp

Comment:

--

DatabaseConnectionsForThreadsAndNewPool

@@ -24 +24 @@
 This proposal will add the following calls to the !ResourceManager to support threads that need a database connection in GeoNetwork/Jeeves:
 
-* openDirect(): essentially does the same as open but does not keep a reference to the Dbms resource in the ResourceManager hashtable
-* close(String name, Object resource): closes the resource from the named resource provider
+ * openDirect(): essentially does the same as open but does not keep a reference to the Dbms resource in the ResourceManager hashtable
+ * close(String name, Object resource): closes the resource from the named resource provider
 
 In addition the proposal will add:
 
-* a new ResourceProvider to pool database connections which uses the Apache Commons Database Connection Pool (ApacheDBCP.java) - this is a slightly more sophisticated approach to database connection pooling than the homegrown Jeeves DatabasePool.java code
-* threads to support safe background database operations for: increasing popularity of metadata (eg. in metadata show), logging search statistics, indexing metadata records after the servlet has started and potentially many other operations that can be put into the background as threads to not slow down critical operations such as search
-* a configurable ThreadPool that all code can access through the GeonetContext which can be used to manage thread operations eg. place limits on the number of threads that can be executed at any one time    
+ * a new ResourceProvider to pool database connections which uses the Apache Commons Database Connection Pool (ApacheDBCP.java) - this is a slightly more sophisticated approach to database connection pooling than the homegrown Jeeves DatabasePool.java code
+ * threads to support safe background database operations for: increasing popularity of metadata (eg. in metadata show), logging search statistics, indexing metadata records after the servlet has started and potentially many other operations that can be put into the background as threads to not slow down critical operations such as search
+ * a configurable ThreadPool that all code can access through the GeonetContext which can be used to manage thread operations eg. place limits on the number of threads that can be executed at any one time    
 
 === Proposal Type ===