You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jmeter-dev@jakarta.apache.org by ja...@apache.org on 2005/01/27 21:49:21 UTC

[Apache JMeter Wiki] Updated: JMeterRemoteTestingEnhancements

   Date: 2005-01-27T12:49:21
   Editor: KevinHurley
   Wiki: Apache JMeter Wiki
   Page: JMeterRemoteTestingEnhancements
   URL: http://wiki.apache.org/jakarta-jmeter/JMeterRemoteTestingEnhancements

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -36,6 +36,14 @@
 ...although, saying this, it may be more useful if the GUI could cut and paste nodes first (let's run before we can walk)  -- Craig Pugsley 12/3/03
 
 ----
+= Remote Testing Set Up =
+Would it be feasible to have the remote server "push" its IP address to the controlling client?
+
+
+  -- KeivnHurley 01/27/2005
+
+----
+
 = Serialisation =
 At present, when a script is sent to the remote server for execution, AFAIK the entire tree is serialised and reconstructed at the other end. This places a lot of burden on developers to make sure that objects are serialisable. Since there is already a convenient representation for a test (i.e. the JMX format) it seems to me that we should make use of it and ship that across instead. It would mean that the remote installation would need to have all the appropriate classes present, but that is probably true anyway.  It should reduce the amount of data sent. It would probably get rid of some of the incompatibilities that occur. I read somewhere recently (probably Effective Java by Joshua Bloch) that hash values are not _guaranteed_ to be the same for different JVMs, nor even between runs of a JVM, which might explain some problems users have reported.["sebb"]
 

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