RPCEchoToolDoc.tioga
Hal Murray, January 22, 1986 11:20:28 pm PST
RPC Echo Tool
CEDAR 6.0 — FOR INTERNAL XEROX USE ONLY
RPC Echo Tool
Hal Murray
© Copyright 1985, 1986 Xerox Corporation. All rights reserved.
Abstract: RPCEchoTool runs simple RPC tests and prints a response time histogram.
Created by: Hal Murray
Maintained by: Hal Murray <Murray.PA>
Keywords: RPC, Echo, Response time
XEROX   Xerox Corporation
    Palo Alto Research Center
    3333 Coyote Hill Road
    Palo Alto, California 94304

For Internal Xerox Use Only
When you first run it, RPCEchoTool exports the RPCEcho interface (by setting the connect site in your GV name) and registers the RPCEcho command with the CommandTool. The RPCEcho command creates another instance of an RPCEcho. (You can happily run several at the same time.) Each instance of an RPCEcho has the following switches and command bottons:
Target
This is the name of the machine you want to talk to. You can also test some of the RPC Binding code by setting the connect site in some GV individual (yours works) and then using that name (with registry) as the target.
Stop
Stop stops the current test. It will print a few quick counts and a histogram of response times.
Simple, 10 Wds, Pull, Push, Page, 10 Pages, Atom, Rope
These are the actual tests.
Simple is a procedure with no args.
10 Wds has 10 words of parameters and 10 words of results.
Pull has 256 words of results.
Push has 256 words of parameters.
Page has 256 words of parameters and results.
10 Pgs has 10 pages of parameters and 10 pages of results. (This is the only multi page test.)
Atom has a single ATOM as a parameter.
Rope has a single rope as a parameter.
Look at the code if you are really curious and/or feel free to add more tests.
When you run RPCEchoTool, it will set up Target to talk to itself. If you want to talk to another machine, start the user side first, then start the server. The user will export the interface to your GV Name, but so will the server. The last one wins.
Krocks
If you start a second test without stopping the first one you will get a debugger window when you (eventually) poke Stop. ABORTing seems to work.