rpcservice(3i) [debian man page]

RpcService(3I)						    InterViews Reference Manual 					    RpcService(3I)

NAME

       RpcService - support RPC between a service and its clients

SYNOPSIS

       #include <Dispatch/rpcservice.h>

DESCRIPTION

       An  RpcService  (actually,  an  instance  of a derived class) creates a port and listens to it for connections from clients.  When a client
       opens a connection, the RpcService will create a reader to handle RPC requests from the connection.

CONSTRUCTORS

       RpcService(int port)
       RpcService(const char* path, int port = 0)
	      Start up an RPC service.	If a filename is given, record the RPC service's hostname and port number in it so clients can contact the
	      service.	If ``port'' is zero, the next free port number will be used.

PUBLIC OPERATIONS

       void run()
       void quitRunning()
	      Read  RPC  requests  continuously  until	``quitRunning()'' terminates the loop.	If you're using InterViews, you don't have to call
	      ``run()'' since the InterViews event-reading code will also read RPC requests.

PROTECTED OPERATIONS

       virtual void createReader(int fd) = 0
	      You must define this function in a derived class in order to start servicing RPC requests from a new client.  Typically all you have
	      to  do is to construct a reader using the passed file descriptor and make the reader responsible for deleting itself when it notices
	      that the connection has been closed by the client.

SEE ALSO

       Dispatcher(3I), RpcReader(3I), RpcRegistry(3I)

InterViews							   27 March 1991						    RpcService(3I)

RpcHdr(3I)						    InterViews Reference Manual 						RpcHdr(3I)

NAME

       RpcHdr - header for remote procedure calls

SYNOPSIS

       #include <Dispatch/rpchdr.h>

DESCRIPTION

       An  RpcHdr enables an RPC request to be sent or received.  To send an RPC request, you would insert an RpcHdr into an rpcstream followed by
       any arguments and then flush the rpcstream if you wanted the request to be sent immediately.  The rpcstream automatically fills in each RPC
       request's  length  field.  To receive an RPC request, you would extract an RpcHdr from an rpcstream and examine the ``request()'' member to
       determine which additional arguments need to be extracted as well.  You can examine the ``ndata()'' member too if you need to estimate  how
       much space to allocate.

CONSTRUCTORS

       RpcHdr(void* writer, int request)
       RpcHdr(int request)
       RpcHdr()
	      Construct  an  initialized  header  for an outgoing RPC request (first two constructors) or construct an uninitialized header for an
	      incoming RPC request (third constructor).  To initialize the header, you'll have to store the request's protocol	number.   You  can
	      also store the address of the writer sending the RPC request if you want to route the RPC request to a specific reader on the peer's
	      side.

PUBLIC OPERATIONS

       unsigned long reader()
       int request()
       unsigned int ndata()
	      Get information about the RPC request.  ``reader()'' identifies the reader which should handle the RPC request.  ``request()'' iden-
	      tifies  the  action  that should be performed.  ``ndata()'' gives the number of data bytes following the header, which may be useful
	      for estimating the amount of space that must be allocated to store an argument.

SEE ALSO

       RpcReader(3I), RpcWriter(3I), rpcstream(3I)

InterViews							   27 March 1991							RpcHdr(3I)