Changeset 3403
- Timestamp:
- Oct 13, 2007, 5:39:15 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/ipcproto.txt
r3401 r3403 8 8 The IPC protocol is used to allow processes to control or retrieve 9 9 information from Transmission frontend, such as transmission-daemon, 10 or the GTK+ or Mac OS X frontends. This communication is done10 or the GTK+ or Mac OS X frontends. This communication is done 11 11 over a unix-domain socket file such as 12 12 ~/.transmission/daemon/socket. In this document the Transmission … … 16 16 Once a client connects to the server's socket, messages may be 17 17 exchanged until either end closes the connection. Messages contain an 18 32-bit payload length, encoded as 8 bytes of ASCII hex idecimal,18 32-bit payload length, encoded as 8 bytes of ASCII hexadecimal, 19 19 followed by the payload. Upper, lower, or mixed case for the length 20 are all acc petable and must be handled correctly. Payload lengths20 are all acceptable and must be handled correctly. Payload lengths 21 21 greater than 2^31 - 8 (ie: 2147483640 decimal, 7FFFFFF8 hex) are not 22 22 allowed.
Note: See TracChangeset
for help on using the changeset viewer.