Generic Function | Package: net.rpc | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## rpc-open-client

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*`. Return values are described in the body of the description.

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. Note that the value of the re-connect keyword argument to make-rpc-client can affect the behavior of this function.

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 no-op for datagram connections.

See also rpc.htm for general information on the Remote Procedure Call utility in Allegro CL.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version