| Allegro CL version 6.2 Object described on page has changed in 6.2 | |||||||||
Arguments: (port rpc-socket-port) &key confirm
This function actually makes a connection based on the parameters
stored in the port instance specified by the
port. Any keyword arguments are used to update
the port instance slots. See ropen, which operates on the
default RPC port bound to the variable *rpc-port*.
When the port is a subclass of with-rpc-port-enabler (such as
rpc-socket-port-with-enabler), and a
passcode was defined in the call to make-rpc-client (or in this
argument list), we send an :enable-client request
as soon as the connection to the server is established.
If the passcode is nil, then the application
must call rpc-enable-client explicitly.
The confirm keyword argument: when this argument
is non-nil, the Lisp RPC protocol includes
additional confirmation messages that track the progress of a remote
call in more detail (see rpc-query for more details). The
default value is nil.
A non-nil value may be applicable when using
a very slow network connection. In such cases more detailed progress
information could be useful.
This argument was not available in releases prior to 6.2, where this
function worked as if this argument was specified non-nil.
Arguments: (port rpc-datagram-port) &key
This method is a noop for datagram connections.
See also rpc.htm for general information on the Remote Procedure Call utility in Allegro CL.
Copyright (c) 1998-2002, Franz Inc. Oakland, CA., USA. All rights reserved.
Documentation for Allegro CL version 6.2. The object described on this page has been modified in the 6.2 release; see the Release Notes.
Created 2002.2.26.
| Allegro CL version 6.2 Object described on page has changed in 6.2 | |||||||||