From: Nemo <nemo.mbox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] streams
Date: Mon, 21 Feb 2011 00:25:38 +0100 [thread overview]
Message-ID: <E85E1C40-0321-48B1-9CC5-2F913CAEC117@gmail.com> (raw)
In-Reply-To: <96B1444A-B40A-4F42-A387-1129C87D1387@gmail.com>
> i did read it before asking, and i'm still wondering why
> not mux tcp instead (provided you dont want/need that extra feature
> or dont implement it that way)
>
>
> On Feb 20, 2011, at 10:59 PM, Russ Cox <rsc@swtch.com> wrote:
>
>> On Sun, Feb 20, 2011 at 11:55 AM, Nemo <nemo.mbox@gmail.com> wrote:
>>> why not mux tcp instead?
>>
>> See the paper. Among other things, independent flow control
>> on the different sub-streams.
>>
>> http://www.brynosaurus.com/pub/net/sst-abs.html
next prev parent reply other threads:[~2011-02-20 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 1:35 Charles Forsyth
2011-02-20 16:55 ` Nemo
2011-02-20 21:37 ` erik quanstrom
2011-02-20 21:59 ` Russ Cox
[not found] ` <96B1444A-B40A-4F42-A387-1129C87D1387@gmail.com>
2011-02-20 23:25 ` Nemo [this message]
2011-02-21 18:53 ` Nemo
2011-02-21 20:41 ` Mechiel Lukkien
2011-02-22 10:15 ` roger peppe
2011-02-22 13:25 ` erik quanstrom
2011-02-22 13:44 ` roger peppe
2011-02-21 0:01 ` Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E85E1C40-0321-48B1-9CC5-2F913CAEC117@gmail.com \
--to=nemo.mbox@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).