From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9ttp
Date: Thu, 8 Sep 2011 13:35:47 -0700 [thread overview]
Message-ID: <20110908203547.C1CF1B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 08 Sep 2011 13:14:47 PDT." <CAL4LZyj6F4HwvrnM+nEyLjGsXa8j+Vt+7eqHPjmK54SjRZCeig@mail.gmail.com>
On Thu, 08 Sep 2011 13:14:47 PDT John Floren <john@jfloren.net> wrote:
> On Thu, Sep 8, 2011 at 12:44 PM, Bakul Shah <bakul@bitblocks.com> wrote:
> >
> > Is there a way to distinguish between files backed by real
> > storage & synthetic files? Seems to me that the server
> > wouldn't know if you pipelined multiple read/write requests on
> > a given connection (in-order delivery). May be the client can
> > do read-ahead of N blocks. But one issue with read-ahead /
> > write-behind is the problem of head of line blocking --
> > further non-r/w requests queue up behind them. That is why FTP
> > uses a control connection for all the commands & responses but
> > data is delivered on a fresh tcp connection.
>
> See my thesis for an FTP-like extension to 9P
> (https://bitbucket.org/floren/tstream/src/67c7419ad84a/documents/Thesis.pdf)
> in which 9P messages are used to negotiate a separate TCP data stream,
> avoiding the blocking problem. It achieved transfer performance
> equivalent to that of HTTP over a high-latency link.
>
> Deja vu here--I know we just discussed this about a month ago :)
Deja vu all over again. We seem have this discussion every N months.
But why do you need to extend the protocol? Just use a new
connection for every file from a local proxy or something! I
will have to read your thesis.
next prev parent reply other threads:[~2011-09-08 20:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:36 s s
2011-09-08 8:51 ` hiro
2011-09-08 16:21 ` David Leimbach
2011-09-08 9:09 ` dexen deVries
2011-09-08 9:17 ` Steve Simon
2011-09-08 9:22 ` dexen deVries
2011-09-08 12:34 ` hiro
[not found] ` <CAFSF3XN_NcKfMzugkhoj2CTaBF6Gfdke0XstEjPqcjr9FswpPw@mail.gmail.c>
2011-09-08 12:54 ` erik quanstrom
2011-09-08 13:04 ` dexen deVries
2011-09-08 16:24 ` David Leimbach
[not found] ` <CAJJ04x7xC4iuqm0HOzKN-Jb3FSmg8w1E+1Lc06pYaOm_diBNsQ@mail.gmail.c>
2011-09-08 16:31 ` erik quanstrom
2011-09-08 16:56 ` John Floren
2011-09-08 16:59 ` ron minnich
2011-09-08 17:18 ` David Leimbach
[not found] ` <CAP6exYJSScKcavDvR55KqJyG5-GphLQxV_+-WuwzgU3CH0pV8w@mail.gmail.c>
2011-09-08 17:20 ` erik quanstrom
2011-09-08 17:28 ` EBo
2011-09-08 19:44 ` Bakul Shah
2011-09-08 20:14 ` John Floren
2011-09-08 20:35 ` Bakul Shah [this message]
2011-09-08 20:43 ` Francisco J Ballesteros
2011-09-08 22:49 ` Bruce Ellis
2011-09-08 23:19 ` Venkatesh Srinivas
2011-09-08 23:29 ` ron minnich
2011-09-08 23:48 ` Venkatesh Srinivas
2011-09-09 0:18 ` Eric Van Hensbergen
[not found] ` <CAP6exYKARAZWWWXfK6myj+y47k3XmNnyF4z17zuHOZHczxDOhw@mail.gmail.c>
2011-09-08 23:32 ` erik quanstrom
2011-09-08 23:51 ` Venkatesh Srinivas
2011-09-09 8:13 ` Charles Forsyth
2011-09-09 9:26 ` Bruce Ellis
2011-09-09 9:36 ` dexen deVries
2011-09-09 11:26 ` Bruce Ellis
2011-09-08 20:18 ` erik quanstrom
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=20110908203547.C1CF1B827@mail.bitblocks.com \
--to=bakul@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).