jakarta-jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-jmeter Wiki] Update of "FutureReleases" by JMeterAdmin
Date Wed, 17 Oct 2007 21:02:12 GMT
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

------------------------------------------------------------------------------
   * Remove unnecessary code duplication in "SOAP/XML-RPC sampler", rather use code inherited
from HTTPSampler2. This is almost done, not committed to svn (Alf Hogemark)
    * Add unit tests for SOAP/XML-RPC sampler
    * Change name exposed to use to "SOAP/XML-RPC/REST sampler"
-  * Make it possible to send file content for HTTP GET, PUT and DELETE using "HTTP Sampler"
and "HTTP Sampler 2", and therefore also "SOAP/XML-RPC sampler"
+  * Make it possible to send file content for HTTP GET, PUT and DELETE using "HTTP Sampler"
and "HTTP Sampler 2", and therefore also "SOAP/XML-RPC sampler" <= some of this ha been
done
   * Make Axis2 / XFire / CFX Sampler, and possible retire existing "Webservice(SOAP) sampler".

    * A bit unsure about this, not sure what benefit is over "SOAP/XML-RPC Sampler".
    * Will we really be testing Axis / XFire client side peformance here ?
@@ -120, +120 @@

    * What are the risks with continuing to use Avalon, if Avalon is not maintained anymore
?
    * Remark: Http``Components project is considering migrating Http``Client 4.0 branch off
Commons Logging to another logging framework as Commons Logging currently appears unmaintained
and the prospects of its further development remain unclear. [Does it need any development?
sebb] It may be worthwhile to ensure both projects use the same logging framework / compatible
logging frameworks. [Agreed: sebb]
   * Upgrade to httpclient4 ? httpclient4 is still only in Alpha. Should / could we have one
sampler class using httpclient3 and one httpclient4 ?
-  * Remove some code in HTTPSampler, which is there fore workaround for httpclient3.0 bug,
which has been fixed in httpclient3.1
   * Reorganise documentation
    * component_reference is getting much too big. This will require changes to the help system.
    * sort functions and component ref into more logical order (currently chronological)
@@ -161, +160 @@

    * could be new sampler GUI with new underlying test elements
    * but it would be nice if existing test plans were converted into the new sampler. Looked
at this a while back, but got stuck with XStream aliasing, which has to be one-to-one at present.
However, the code change to Save``Service to remove the class loading should make it possible
to have multiple aliases for a single class. That might be sufficient, otherwise we'll need
a suitable converter.
    * I think the GUI should just contain a dropdown "Client implementation", with values
like "Java JRE", "HTTPClient 3.1", "HTTPClient 4.0" etc.
-  * Improve "org.apache.jmeter.JMeter" class by removing the hack in "ListenToTest", which
causes JMeter to always sleep 5 seconds before exiting when run in batch
-   * I think this relates to how threads are closed and lingering samples are handled. How
is it solved in the "GUI" mode ?
   * GUI code refactor
    * there are various table implementations, could they be combined?
    * perhaps the table models could also be combined?
@@ -172, +169 @@

   * Consider renaming Thread``Group as JMeter``Thread``Group - or User``Group ? - to avoid
confusion with java.lang.Thread``Group
   * Documentation refers to threads and/or users in different places; replace by users -
or users(threads) - everywhere?
   * Test elements need access to Thread``Group and Test``Plan for co-ordinating counts etc
per-group and per-plan. Not much distinction is currently made between per-group and per-plan.
-  * Does it make sense to use existing samplers in the JMeter proxy? These may change the
request or response. Might be better to use low-level socket routines instead?
  
  = Release strategy =
  
@@ -203, +199 @@

   * 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)
   * HTTP Cookie Manager should not clear static cookies each iteration
+  * Remove some code in HTTPSampler, which is a workaround for httpclient3.0 bug, which has
been fixed in httpclient3.1
+  * Improve "org.apache.jmeter.JMeter" class by removing the hack in "ListenToTest", which
causes JMeter to always sleep 5 seconds before exiting when run in batch
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org


Mime
View raw message