From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] streams
Date: Sun, 20 Feb 2011 16:01:37 -0800 [thread overview]
Message-ID: <20110221000137.E278B5B58@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 20 Feb 2011 01:35:28 GMT." <e9dcbb4575bd9e996107205d6ef24358@terzarima.net>
On Sun, 20 Feb 2011 01:35:28 GMT Charles Forsyth <forsyth@terzarima.net> wrote:
> i think it might be helpful to have a transport protocol along the lines
> of Bryan Ford's SST, which allows a stream to create substreams
> with separate flow control and other attributes. a primary 9p stream
> might create a substream for a large Tread or Twrite.
> the facility could be emulated for existing protocols, although addressing
> puzzles make that trickier that one might like. the demo SST implementation
> was built on UDP. a service to resolve addressing puzzles might be useful too
> .
Thanks. Read the paper but need to think about it more....
Seems quite interesting. The idea of using substreams for
large xfers is clever! A stream analogue of worker threads.
Not sure what addressing puzzle you are talking about.
prev parent reply other threads:[~2011-02-21 0:01 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
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 [this message]
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=20110221000137.E278B5B58@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).