// xmlBlaster/demo/javaclients/Latency.java package javaclients; import java.util.logging.Logger; import java.util.logging.Level; import org.xmlBlaster.util.*; import org.xmlBlaster.client.I_Callback; import org.xmlBlaster.client.key.SubscribeKey; import org.xmlBlaster.client.key.PublishKey; import org.xmlBlaster.client.key.UpdateKey; import org.xmlBlaster.client.qos.ConnectQos; import org.xmlBlaster.client.qos.DisconnectQos; import org.xmlBlaster.client.qos.PublishQos; import org.xmlBlaster.client.qos.SubscribeQos; import org.xmlBlaster.client.qos.UpdateQos; import org.xmlBlaster.client.I_XmlBlasterAccess; import org.xmlBlaster.util.MsgUnit; /** * Measure the brutto roundtrip latency of a message publish and update. *
* Invoke examples (put xmlBlaster.jar in your CLASSPATH): ** java org.xmlBlaster.Main * java javaclients.Latency -numSend 100 **
* java javaclients.Latency -numSend 100 -bootstrapHostname server.xmlBlaster.org * or if you have a dynamic IP: * java javaclients.Latency -numSend 100 -bootstrapHostname server.xmlBlaster.org -dispatch/callback/plugin/ior/hostname**
* java javaclients.Latency -numSend 100 -dispatch/connection/protocol XMLRPC -dispatch/connection/plugin/xmlrpc/hostname server.xmlBlaster.org -dispatch/callback/plugin/xmlrpc/hostname* * Results, for one round trip including publish -> processing in xmlBlaster -> update -> parsing in client (600 MHz AMD Linux): **