rpcstream(3i) [debian man page]

rpcstream(3I)						    InterViews Reference Manual 					     rpcstream(3I)

NAME

       rpcstream - iostreamb specialized to RPC requests

SYNOPSIS

       #include <Dispatch/rpcstream.h>

DESCRIPTION

       rpcstream,  irpcstream,	and  orpcstream specialize iostream, istream, and ostream, respectively, to RPC requests.  That is, the associated
       streambuf will be an rpcbuf.  Conversions will be formatted (that is, ASCII) so datums will need to be separated by space characters.

CONSTRUCTORS

       rpcstream()
	      Construct an unopened rpcstream.

PUBLIC OPERATIONS

       void listen(int port)
       void connect(const char* host, int port)
	      Create a connection.  Any failure sets ios::failbit in the error state.

       int accept()
	      Accept a pending connection and return the new file descriptor.

       void attach(int fd)
	      Attach to a pre-existing connection.

       void close()
	      Break a connection.  The error state is cleared except on failure.

       void nonblocking(boolean)
       void verbose(boolean)
	      Enable or disable non-blocking I/O and/or printing of error messages.

       rpcbuf* rdbuf()
	      Return a pointer to the rpcbuf created by the rpcstream.

       boolean incomplete_request()
       void incomplete_request(boolean)
	      Get or set a flag.  Used by the operations that insert an RpcHdr into an rpcstream or extract an RpcHdr from an rpcstream.

SEE ALSO

       IOS.INTRO(3C++), iostreamb(3I), rpcbuf(3I)

InterViews							   27 March 1991						     rpcstream(3I)

RpcPeer(3I)						    InterViews Reference Manual 					       RpcPeer(3I)

NAME

       RpcPeer - support bi-directional RPC between two services

SYNOPSIS

       #include <Dispatch/rpcpeer.h>

DESCRIPTION

       An  RpcPeer (actually, an instance of a derived class) tries to open a connection to another RpcPeer.  If the other RpcPeer is not yet run-
       ning, the RpcPeer will create its own port and wait for the other RpcPeer to open a connection.	When either RpcPeer  opens  a  connection,
       each RpcPeer will create both a reader and a writer so each RpcPeer can send RPC requests to its opposite over the same connection.

CONSTRUCTOR

       RpcPeer(const char* lPath, int lPort = 0)
	      Store  the arguments for later use since a base constructor can't call a derived class's virtual function.  The derived class's con-
	      structor should call ``init'', described below.

       void init(const char* rPath)
	      Find the host name and port number registered by the other RpcPeer and try to open a connection to it.  If it's not running,  create
	      our own port and wait for the other RpcPeer to open a connection.

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 boolean createReaderAndWriter(const char* rHost, int rPort) = 0
       virtual void createReaderAndWriter(int fd) = 0
	      You must define both functions in a derived class in order to start reading and writing RPC requests over the connection.  Typically
	      both functions would create a writer using the given parameters and then attach a reader to the writer's rpcstream.

SEE ALSO

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

InterViews							   27 March 1991						       RpcPeer(3I)