Attaches a ChIPS client to the specified server.
-
server_id - the id of the ChIPS server to query; generally a
string such as "ChipsServer_17334_1".
The connect command is used to attach a ChIPS client to a ChIPS
server process. When a ChIPS command is invoked which requires
the server (almost all commands require the server), a ChIPS
server is automatically launched. Users can connect to an
existing server in order to modify the ChIPS from a different
application. For example, a user may create a plot from the CIAO
GUI Prism, then connect to the server from an xterm and
continue working in that ChIPS session.
The user may specify a server id to connect to a specific
server which is running. A list of existing servers can be
determined by the list_servers command
("ahelp list_servers").
If no server id is supplied, then ChIPS will attempt to
connect to an existing server. This will not work if multiple
servers are running on the system.
If the ChIPS session is already attached to a server (either
through a connect call or by creating plots) and the user issues
a connect command, ChIPS automatically disconnects from the
current server. Note that if that server only has one ChIPS
session attached to it, disconnecting from it causes it to
close and any work done during the session is discarded.
chips> get_server_id;
ChipsServer_6979_1
chips> list_servers;
['ChipsServer_6979_1', 'ChipsServer_20997_1']
chips> connect("ChipsServer_20997_1");
The client is initially connected to the server with id
"ChipsServer_6979_1". The connect request reconnect ChIPS with
a new server.
chips> get_server_id;
chips> list_servers;
['ChipsServer_5643_1']
chips> connect();
The client is initially not connected to any server. There
is another server running. The connect command automatically
attaches itself to the server that is running.
The connect function has been updated so that if no server id
is specified it will attempt to connect to an existing server.
If multiple servers or no servers are running, an error is
returned.
|