Lines Matching defs:queues
99 These connections (referred to as peer queues) can be of two types:
102 \item[synchronous] These queues are synchronised by the control
108 \item[asynchronous] These queues can perform I/O operations that are not
252 subsequent connections (for ec_rpc and any peer queues) are checked to
405 As discussed in section~\ref{remoteprotobasic}, peer queues can be formed
407 provides for the creation and closing of these queues on both sides.
409 The handling of data on these queues are performed by {\it data handlers},
419 \subsection{Synchronous peer queues}
438 these queues appear uni-directional to the user, i.e. data can be either
469 \subsection{Asynchronous peer queues}
471 I/O operations on these queues do not need to be controlled by the remote
473 protocol, so that the remote interface can keep track of these queues.
478 block on these queues. They are provided to allow asynchronous transfer of
766 synchronous queues, bidirect for asynchronous queues). The client socket is
903 queues) to the remote side, and clean up the information associated with the
1130 asynchronous queues as well. In this case, an event handler is directly
1369 definable event will be raised in {\eclipse}, just before the remote queues
1485 queues, it is ignored for asynchronous queues), {\tt Event} is the name of