Lines Matching +full:- +full:- +full:-

2 --- a replacement for aproto -------------------------------------------
17 The protocol is designed to be straightforward and well-defined enough 
25 --- protocol overview and basics ---------------------------------------
50 The identifiers "local-id" and "remote-id" are always relative to the
56 --- CONNECT(version, maxdata, "system-identity-string") ----------------
66 hard-coded maxdata=4096, so CONNECT and AUTH packets sent to a device must not
79 kind of unique ID (or empty), and banner is a human-readable version
82 --- STLS(type, version, "") --------------------------------------------
91 --- AUTH(type, 0, "data") ----------------------------------------------
107 possible, an on-screen confirmation may be displayed for the user to
111 --- OPEN(local-id, 0, "destination") -----------------------------------
116 identified by local-id that it wishes to connect to the named
117 destination in the message payload.  The local-id may not be zero.
126 * "tcp:<host>:<port>" - host may be omitted to indicate localhost
127 * "udp:<host>:<port>" - host may be omitted to indicate localhost
129 * "local-dgram:<identifier>"
130 * "local-stream:<identifier>"
131 * "shell" - local shell service
132 * "upload" - service for pushing files across (like aproto's /sync)
133 * "fs-bridge" - FUSE protocol filesystem bridge
136 --- READY(local-id, remote-id, "") -------------------------------------
141 identified by local-id is ready for write messages and that it is
142 connected to the recipient's stream identified by remote-id.
144 Neither the local-id nor the remote-id may be zero.
146 A READY message containing a remote-id which does not map to an open
148 closed while this message was in-flight.
150 The local-id is ignored on all but the first READY message (where it
151 is used to establish the connection).  Nonetheless, the local-id MUST
155 --- WRITE(local-id, remote-id, "data") ---------------------------------
160 remote-id.  The payload MUST be <= maxdata in length.
162 A WRITE message containing a remote-id which does not map to an open
164 closed while this message was in-flight.
173 --- CLOSE(local-id, remote-id, "") -------------------------------------
178 sender's stream (local-id) and the recipient's stream (remote-id) is
179 broken.  The remote-id MUST not be zero, but the local-id MAY be zero
182 A CLOSE message containing a remote-id which does not map to an open
184 already been closed by the recipient while this message was in-flight.
191 --- SYNC(online, sequence, "") -----------------------------------------
210 --- message command constants ------------------------------------------
223 --- implementation details ---------------------------------------------
238 always treat message header values as native-endian.
240 The bridge program will be able to have a number of mini-servers
242 "shell", "fs-bridge", etc) and upon receiving an OPEN() to such a
247 --- simplified / embedded implementation -------------------------------
250 support a smaller, fixed number of channels using pre-assigned channel
266 --- future expansion ---------------------------------------------------
283 ------------------------------------------------------------------------
285 --- smartsockets -------------------------------------------------------
294 client: <hex4> <service-name>
297 client: <hex4> <service-name>