In message <_A4148@delegate-en.ML_> on 09/23/08(20:59:55)
you "Andre E." <firstname.lastname@example.org> wrote:
|Hi again...I'm sorry, it's Session Control Protocol, not Stream Control Protocol.
|Will future versions of delegate by any chance contain an implementation
|of the SESSION Control Protocol?
| * http://tools.ietf.org/html/draft-evans-v2-scp-00
| * http://www.ibiblio.org/ses/scp.html
Why you need it?
I thought a common session control layer as in the OSI reference model
should have been introduced when HTTP upgraded from 1.0 to 1.1 in which
"Keep-Alive" became the default. If introduced, I think it might have
made things simple and clear including parallel and/or pipelined sessions
on a single TCP connection, not only for HTTP but for arbitrary protocols,
reducing the latency between peers with long RTT.
I remember that someone suggested such a simple and generic session control
for HTTP/1.1 but it is not supported, but "chunked" and "content-length"
based message delimiter just for a single session is adopted.
But anyway I needed some kind of multiplexing on a TCP connection,
I made several experimental protocols including Teleport/Vehicle, ThruWay,
and SockMux. I'm using the last one yet to connect between DeleGates as
9 9 Yutaka Sato <email@example.com> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller