Changes between Version 4 and Version 5 of DatabaseConnectionsForThreadsAndNewPool

Timestamp:

01/31/11 23:17:06 (14 years ago)

Author:

simonp

Comment:

--

DatabaseConnectionsForThreadsAndNewPool

@@ -22 +22 @@
 However there is a need for threads that want a database connection to obtain a connection and hold that connection open even though the service that started the thread may have closed.
 
-This proposal will add the following calls to the !ResourceManager to support threads that need a database connection in GeoNetwork/Jeeves:
+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
+ * 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 Jeeves DatabasePool.java code
+ * 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 Jeeves code in jeeves/src/main/java/jeeves/resources/dbms/DbmsPool.java
  * 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 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 ===
- * '''Type''': Core Change and change to coding procedures ie. use new ResourceManager calls for threads that need database connections, use ThreadPool to execute threads
+ * '''Type''': Core Change and change to coding procedures ie. use new !ResourceManager calls for threads that need database connections, use !ThreadPool to execute threads
  * '''App''': !GeoNetwork
  * '''Module''': Kernel and services