ComputeServerControl.mesa
Compute Server Control interface for the Summoner. This is an interface from the rest of the Cedar world to the Server. This is not an RPC interface, and is used on the Server machine.
Last Edited by: Bob Hagmann, May 15, 1985 8:23:50 am PDT
Hal Murray, March 22, 1986 9:12:47 pm PST
Copyright © 1984 by Xerox Corporation. All rights reserved.
DIRECTORY
Commander,
Rope,
RPC;
ComputeServerControl: CEDAR DEFINITIONS =
BEGIN
NotSummonerProcess: ERROR ;
MyNetAddressRope: Rope.ROPE;
The Pup address of this machine as a rope.
StartUpServer: PROC [controllerName: Rope.ROPENIL, remoteCommandDirectory: Rope.ROPENIL, localCommandDirectory: Rope.ROPENIL] RETURNS [msg: Rope.ROPENIL] ;
Start up a server under the controller specified by "controllerName". If "controllerName" is NIL, use the name from the profile entry for Summoner.ControllerName. If that is NIL, use "PaloAlto.summoner". "remoteCommandDirectory" is the directory on a file server where the packages reside. If NIL, it is taken from the profile entry for Summoner.RemoteCommandDirectory. If that is also NIL, "<Summoner>Packages>" on the system host is used. "localCommandDirectory" specifies the directory on the workstation to be used for file storage. If "localCommandDirectory" is NIL, use the name from the profile entry for Summoner.LocalCommandDirectory. If that is NIL, use "///Summoner/Packages/".
ShutDownServer: PROC [] RETURNS [] ;
Server is shut down.
Register: PROC [key: Rope.ROPE, version: Rope.ROPENIL, proc: Commander.CommandProc, doc: Rope.ROPENIL, clientData: REF ANYNIL];
A bcd file when it is run must call Register to register the existence of a command. The commands registered must include all commands in the .remoteCommands file for the package. This is identical to the Register PROC in the ComputeServerServer interface. In fact, the other Register simply calls this one when the Server code is running on the workstation. The ComputeServerServer interface is assumed to always be available, and is used for user interfaces where the user may or may not want to use the Compute Server. This interface is to be used when the client "knows" that the Compute Server is in use.
END.
Bob Hagmann May 3, 1985 12:49:19 pm PDT
changes to: ComputeServerControl