rpc-open-listener

Arguments: (server rpc-socket-server) &key confirm name open local-host local-port limit max timeout home re-connect begin connect-action connect-function connect-args debug verbose mode export message-timeout message-length certificate key other-certificates tester passcode

Arguments: (server rpc-datagram-server) &key confirm

This function starts a Lisp process that accepts connections from a passive socket. The newly created process (a port instance) is returned but nil is returned if the process could not be started. This is the typical method of maintaining an RPC connection both in the stream socket and datagram protocols.

The keyword arguments are the same as make-rpc-server, and are used to update the settings in the server instance. See make-rpc-server for information on the keyword arguments. Only confirm is discussed here.

When a connection is accepted, a server port is created and the connect-function is called if it is specified (see rpc-open-server for more information on the connect-function). The limit count is decremented if limit is non-nil. When limit reaches zero, new connections are no longer accepted. The decremented limit persists over closing and re-opening a listener. To reset the limit count, add the limit keyword argument in the call to rpc-open-listener.

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.

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.