documents/embedding/embremoteproto.tex

68 \item[Control] This connection is used to control the remote
77 identified by its control
82 control}. When a side has control, it is able to send messages to the other
83 side via the control connection. The side that does not have control
84 waits for messages to arrive on the control connection. On the {\eclipse}
85 side, execution is suspended while it does not have control. In general, once a
86 control message is sent, the control is passed to the other side, and the
92 can only be done while the remote side has control, and when the goal is
93 issued, a message is sent via the control connection to the {\eclipse}
94 side, and control is passed to the {\eclipse} side. Control is passed back
102 \item[synchronous] These queues are synchronised by the control
109  co-ordinated by the control
111 without transferring control. In fact, if the remote language is
113 side has control. Note that asynchronous I/O
141 \item Initialisation and handshaking: the control connection is
164 connections between the two sides, from the control connection to the peer
173 \item {\eclipse} side: a socket server for the control connection is
175 user. It then waits to accept a socket stream for the control connection
179 \item Remote side: create a client socket stream for the control connection,
183 control socket in EXDR format and flush it. This should be a {\tt
185 \item {\eclipse} side: reads the EXDR version term from the control
191 most 100 seconds after the control connection is established for the remote side's version: after
192 this the {\eclipse} side disconnects the control connection and raises out
197 \item Remote side: write the `pass-term' in EXDR format on the newly created control
206 \item Remote side: read from the control connection the {\eclipse} name for the control
211 remote process on the control connection. This should be in EXDR string
216 the control connection) for the ec_rpc connection. This can also time-out.
218 same Port as for the control connection. This stream should be in
221 \item Remote side: read the control connection name again on the remote side, on the
225 \item Remote side: the remote side now has control. Any user-defined initialisations on the remote
227 interaction. The remote side has the control initially. Note that
229 sending the control name on the ec_rpc connection. After the
230 initialisation, {\eclipse} side will suspend and listen on the control
231 connection for the remote side to give control back to the {\eclipse} side.
237 The remote_connect/3 or remote_connect_accept/6 predicate waits for the control to be handed back by
240 side having control.
251 client's hostname, or 'localhost'. After accepting the control connection,
276 %    -Control: the remote side (local) name of the control connection
278 %    -EcSideControl: the ECLiPSe side name for the control connection
281      % control connection
303      % read control name again on Ec_rpc to verify connection
312      % Remote side now has control, call Init to perform application
315      % hand control over to ECLiPSe side...
325 % and then disconnect immediately when ECLiPSe side returns control
332      % control has been given to ECLiPSe side,
333      % wait for ECLiPSe side to return control....
345 of using the protocol by exchanging control messages with the {\eclipse}
347 control is handed back to it. For more details on the messages, see next
379 control. To return control to the remote side, the {\eclipse} side should
390 In this simple example, when control is returned to remote side, it
411 queue. They are triggered by the appropriate control messages, so that a
437 is used in the control messages. To conform to normal {\eclipse} streams,
453 to write data to or read data from the other side via the socket stream), it must have control
455 performing the I/O operation, a control message is sent to the other side to
480 control), and also they allow more efficient transfer of data.
486 control connection, and are in EXDR format. All arguments for the messages
489 particular side when that side has control, and control is handed over
494 other side: control is handed over, the action takes place on the other
495 side, and eventually control is handed back
506 routines would send the appropriate control messages to the {\eclipse}
537 \item[yield] this yields control to the remote side.  The message is used either to
538 implicitly return control to the remote side at the end of an
540 is used to explicitly hand over control to the remote side.
673 queue after sending this message on the control connection, so on receiving
676 control to the {\eclipse} side via a {\bf resume} message.
732 and control is yielded to remote side so that it can provide
741 hands control back to {\eclipse} side by the resume message. The suspended
752 Note that the {\eclipse} side will also listen to the control connection
802 returns control to {\eclipse} via a {\bf socket_connect} message:
828 The {\eclipse} side then returns control to the remote side via a
840 needed for the control messages connected with this peer queue). If instead
843 connection, control is returned to the {\eclipse} side via a {\bf resume}
902 control and ec_rpc connections, and any asynchronous and synchronous
951 \item[resume] this message hands over control from remote side to
952 {\eclipse} side. This is used to either implicitly return control to the
954 side, or to explicitly hand over control to the remote side.
1087 {\eclipse} side will yield control back to the remote side with a {\bf
1118 After sending the message, control is transferred over to the {\eclipse}
1166 After sending the message, control is transferred over to the {\eclipse}
1236 control. The {\eclipse} side will yield control back to the remote side,
1245 yield control back to the remote side with a {\bf yield} message. In this
1331 terminate the attachment while the {\eclipse} side has control. This can
1333 a message can be sent via the control connection on the remote side while
1334 it does not have control. Once the message is sent, the remote side can
1343 by the side that has control, by sending a {\bf disconnect} message to the
1352 it does not have control. For example, in the Tcl remote interface, the
1359 The {\eclipse} side checks the control connection for any unexpected
1360 incoming messages before it sends an outgoing control message. If there is
1374 as the control stream. The event handler for this event is initially
1409 control to the {\eclipse} side. Peer is the name of the control
1438 and Socket. The predicate will create the control and rpc connections
1467 Peer. All connections (control, ec_rpc, synchronous and asynchronous
1472 Explicitly yield control to the remote side Peer. Execution on
1473 {\eclipse} side will be suspended until the remote side returns control to
1475 control. The predicate will abort if the remote side initiates
1478 applications by wrapping the {\tt remote_yield/1} in a \bipref{block/3}{../bips/kernel/control/block-3.html} call.