Subj : MUX
To   : Lawrence Garvin
From : Robert Davies
Date : Sat Sep 22 2001 02:44 pm

Hello Lawrence,

Thanks for your reply!

 LG> Can you expand a bit on your question, Robert?

Sorry no but I can give you the information from the web.

We need lightweight efficient transport for conveying HTTP requests and 
responses. It must support reliable message transport, message fragmentation 
(the ability to send and receive a whole message as a series of partial 
messages), and congestion control as in TCP/IP. It must be able to export an 
API very similar to the BSD socket interface. If implemented on top of TCP/IP, 
or any other reliable byte-stream protocol, it must be able to support multiple 
independent channels or sessions over a single TCP/IP connection, and should be 
bi-directional (no difference between receiving and originating ends of the 
TCP/IP connection). We hope to be able to implement the MUX over TCP/IP, but 
the BSD sockets API may make it too inefficient, and the MUX layer may have to 
be implemented on top of IP (i.e., UDP/IP).

The work is centered at the World Wide Web Consortium (see 
http://www.w3.org/pub/WWW/Protocols/MUX).

 RD>>
 RD>> http://www.parc.xerox.com/istl/projects/http-ng/transport-is
 RD>> sues.ht ml

 LG> What's the URL for?

Thats where I got the info I was wondering if it was in place yet or is it 
still in development.

Cheers

Spasm

---
 * Origin: FrontDoor APX Cardigan Wales (2:250/333.9)

.