Query: rpcservice
OS: debian
Section: 3i
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
RpcService(3I) InterViews Reference Manual RpcService(3I)NAMERpcService - support RPC between a service and its clientsSYNOPSIS#include <Dispatch/rpcservice.h>DESCRIPTIONAn 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.CONSTRUCTORSRpcService(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 OPERATIONSvoid 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 OPERATIONSvirtual 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 ALSODispatcher(3I), RpcReader(3I), RpcRegistry(3I) InterViews 27 March 1991 RpcService(3I)
Related Man Pages |
---|
rpcreader(3i) - debian |
rpcstream(3i) - debian |
rpcbind(8) - netbsd |
portmap(1m) - hpux |
rpc(5) - opendarwin |
Similar Topics in the Unix Linux Community |
---|
Setting com port questions |
socket programing-problem with server |
Redirecting requests from 8153 and blocking access to the same |
RPC Issue |
RPC Issue |