Lines Matching refs:a
2 --- a replacement for aproto -------------------------------------------
13 The host side becomes a simple comms bridge with no "UI", which will
15 a device or emulator that is connected to the bridge.
27 The transport layer deals in "messages", which consist of a 24 byte
28 header followed (optionally) by a payload. The header consists of 6
47 is represented by a quoted string or an empty string if none should be
51 *sender* of the message, so for a receiver, the meanings are effectively
58 The CONNECT message establishes the presence of a remote system.
65 Both sides send a CONNECT message when the connection between them is
66 established. Until a CONNECT message is received no other messages may
67 be sent. Any messages received before a CONNECT message MUST be ignored.
69 If a CONNECT message is received with an unknown version or insufficiently
74 kind of unique ID (or empty), and banner is a human-readable version
81 connect to the sender. If type is TOKEN(1), data is a random token that
82 the recipient can sign with a private key. The recipient replies with an
84 signature verification succeeds, the sender replies with a CONNECT packet.
86 If the signature verification fails, the sender replies with a new AUTH
87 packet and a new random token, so that the recipient can retry signing
88 with a different private key.
98 The OPEN message informs the recipient that the sender has a stream
102 The OPEN message MUST result in either a READY message indicating that
104 a CLOSE message, indicating failure. An OPEN message also implies
105 a READY message sent at the same time.
126 A READY message containing a remote-id which does not map to an open
141 A WRITE message containing a remote-id which does not map to an open
145 A WRITE message may not be sent until a READY message is received.
146 Once a WRITE message is sent, an additional WRITE message may not be
148 a WRITE message that is in violation of this requirement will CLOSE
157 if this CLOSE indicates a failed OPEN.
159 A CLOSE message containing a remote-id which does not map to an open
163 The recipient should not respond to a CLOSE message in any way. The
164 recipient should cancel pending WRITEs or CLOSEs, but this is not a
176 sends a SYNC(0, 0) and starts discarding all messages
178 sends a SYNC(1, token) and continues to discard messages
179 * when the io pump receives a matching SYNC(1, token), it once again
198 will be a select/epoll loop to handle io between various inbound and
202 reading, one for writing) and a datagram socketpair to provide the
212 The bridge program will be able to have a number of mini-servers
214 "shell", "fs-bridge", etc) and upon receiving an OPEN() to such a
215 service, the bridge program will create a stream socketpair and spawn
216 a thread or subprocess to handle the io.
222 support a smaller, fixed number of channels using pre-assigned channel
223 ID numbers such that only one stream may be connected to a bootloader
228 which may be opened to get debug messages from the bootloader and a
240 I plan on providing either a message or a special control stream so that
245 The initial design does handshaking to provide flow control, with a
251 a WRITE or it may defer the READY until the write to the local stream
259 Port 5037 is used for smart sockets which allow a client on the host
260 side to request access to a service in the host adb daemon or in the
262 preceeded by a 4 digit hex length. Upon successful connection an
263 "OKAY" response is sent, otherwise a "FAIL" message is returned. Once