Lines Matching refs:In
153 In more detail, the {\eclipse} predicate remote_connect/3 establishes a
213 being connected to are not from the same version of {\eclipse}. In this
346 Tcl. In particular, it is not possible to request data from the other side
372 In {\eclipse}, the handler goal is invoked using the events mechanism. That
387 \item[Data provider] To provide data that has been requested by the other side. In this
614 know how many bytes will be sent. In this case, {\bf ec_flush} can be
837 In the case where a Tcl data consumer
876 immediate corresponding read on the {\eclipse} side. In fact, no handler
1055 data. In the asynchronous queue, it is generally the programmer's
1169 In an application, after the Tcl side has been attached, typically some
1185 may be initiated from either side. In addition to cleaning up and closing
1406 as the termination of the {\eclipse} side should be handled in {\eclipse}. In
1425 \item In general, reading data via a blocking socket requires the
1449 \item Asynchronous queues are bi-directional. In the embedding interface,
1456 In summary, to write code that will work for both the remote and embedded