| |
| | Message Multiplexing (memux) Charter (Site not responding. Last check: 2007-11-04) |
 | | The length of a message is unrestricted (e.g., not bounded by layer 2 or 3 packet sizes), and the payload of a message is also unrestricted; such a message can be used directly, e.g., as a request or a response in an application-level request/response protocol. |
 | | The MEMUX protocol will be lightweight in these two ways: (1) its overhead, in bytes on the wire, will be low, and (2) opening and closing new message streams, once the byte stream connection is established, will take few bytes and impose no round-trip delays. |
 | | The value of the MEMUX protocol is twofold: (1) it provides a commonly useful service abstraction (bidirectional reliable ordered arbitrary-sized message stream), and (2) the multiplexing achieves the same results as state sharing between parallel TCP streams (which is not widely available today). |
| www.w3.org /Protocols/HTTP-NG/1999/02/mux-Charter-208.html (333 words) |
|