Wireless Village HTTP Get
This message flow simulates a WV session over HTTP over TCP that retrieves a message from a Wireless Village server. It is intended to generate simple WV traffic between the MN and the Network Host node.
When control plane protocols are used, the message flow begins after Data Start Delay timer expires. The MN initiates the TCP connection and the Client Port and Server Port in the message flow define the ports used for the TFTP request.
The WV requests and responses are embedded in the HTTP POST requests and server responses. Since the same HTTP request or response header is used in every message, only the first of each is shown in detail. The WV XML involved in each message is too large to show in the diagram. The request and response names are instead shown and enclosed in angle brackets.
The flow is designed to simulate a client logging in to a WV server and checking for new messages. The server informs the client that a message is available. The client retrieves the message, notifies the server that the message was delivered, and logs out.
In the default configuration, the message flow will repeat once per second while the MN session is active. This assumes that the entire flow can be completed in one second. The flow must complete before the next iteration can begin, even if this results in a slower transaction rate.
Modifying the Message Flow
Since message flow uses WV's text-based XML, you can easily modify the requests and responses if you are familiar with the structure.
-
When using the DATA command, the message content must always finish with a period, and only a period, on the last line.
-
You can simulate a session that sends multiple email messages by enclosing steps 5 — 10 with a Transaction Start/Transaction End pair of commands.
Pipelining can be achieved by clearing the Wait for Response checkboxes in the request messages. The requests will be successively sent without waiting for server responses.
You can specify that random port numbers, in the IANA specified dynamic range of 49152 — 65535, be used by the client by entering a 0 for the Client Port.