Lines Matching refs:is

4 When it comes down to it, aproto's primary purpose is to forward
15 a device or emulator that is connected to the bridge.
17 The protocol is designed to be straightforward and well-defined enough 
35     unsigned data_length;   /* length of payload (0 is allowed)          */
46 detail.  Their format is COMMAND(arg0, arg1, payload) where the payload
47 is represented by a quoted string or an empty string if none should be
61 The version is used to ensure protocol compatibility and maxdata
63 is willing to accept.
70 Both sides send a CONNECT message when the connection between them is
71 established.  Until a CONNECT message is received no other messages may
74 If a CONNECT message is received with an unknown version or insufficiently
78 where systemtype is "bootloader", "device", or "host", serialno is some
79 kind of unique ID (or empty), and banner is a human-readable version
80 or identifier string.  The banner is used to transmit useful properties.
87 and will need to perform a TLS handshake. version is the current version of
95 The AUTH message informs the recipient that authentication is required to
96 connect to the sender. If type is TOKEN(1), data is a random token that
98 AUTH packet where type is SIGNATURE(2) and data is the signature. If the
106 AUTH packet where type is RSAPUBLICKEY(3) and data is the public key. If
140 identified by local-id is ready for write messages and that it is
146 stream on the recipient's side is ignored.  The stream may have been
149 The local-id is ignored on all but the first READY message (where it
150 is used to establish the connection).  Nonetheless, the local-id MUST
162 stream on the recipient's side is ignored.  The stream may have been
165 A WRITE message may not be sent until a READY message is received.
166 Once a WRITE message is sent, an additional WRITE message may not be
168 a WRITE message that is in violation of this requirement will CLOSE
177 sender's stream (local-id) and the recipient's stream (remote-id) is
182 stream on the recipient's side is ignored.  The stream may have
186 recipient should cancel pending WRITEs or CLOSEs, but this is not a
198 is broken.  It was only used internally to the bridge and never valid
203 * when the connection to the remote side is established, the io pump
231 threadpair.  The reason for this is that for usb connections, the
248 For limited environments, like the bootloader, it is allowable to
252 "embedded" version of it is less dynamic.
286 Port 5037 is used for smart sockets which allow a client on the host
288 remote (device) daemon.  The service is requested by ascii name,
290 "OKAY" response is sent, otherwise a "FAIL" message is returned.  Once
291 connected the client is talking to that (remote or local) service.