Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-jmeter Wiki" for change notification.
The following page has been changed by JMeterAdmin: http://wiki.apache.org/jakarta-jmeter/FutureReleases ------------------------------------------------------------------------------ This section is for listing possible enhancements. Describe them briefly. If necessary add bug ids (or links) to clarify. * JDBC connection pooling - possible enhancements - * Add option to use a single connection per-thread (e.g. if Pool Max=0) - * or remove pooling altogether? - does it make sense to share connections between threads, which are supposed to be independent users? * use Apache DBCP instead of Excalibur? * JDBC sampler - use different cache sizes for connection and statement? * How do these really work? * Should the connection cache be a Thread``Local item? - * Need to add debugging to show when cache items are created and destroyed + * Need to add debugging to show when cache items are created and destroyed - difficult for pooled resources * XPath Extractor - add user-declared namespaces * Rework HTTP GUI to make it easier to use and extend * Add HTTP methods dropdown to "SOAP/XML-RPC sampler", bugzilla 42637 @@ -202, +200 @@ * JDBC IN/OUT/INOUT parameters * Save Graphics should prompt before overwriting files * user.properties and system.properties should be read from JMeter launch directory if not found in current directory. + * Add option to use a single connection per-thread (if Pool Max=0) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
