From: Sam Watkins <sam@nipl.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 9p vs http
Date: Mon, 15 Nov 2010 14:25:31 +1100 [thread overview]
Message-ID: <20101115032531.GB27578@opal.ai.ki> (raw)
hi,
I am wondering what you think about the capabilities of 9p compared to
http/1.1. Perhaps this seems like an odd comparison, but I think 9p and http
are broadly similar in purpose and functionality. While writing a simple
webserver, I got to thinking that http is really a very capable protocol.
http is text-based, it supports pipelining and arbitraty metadata. As far as I
know, 9p does not support pipelining nor arbitraty metadata. It seems to me
that these are big advantages for http. 9p supports walking; are there other
things 9p can do which http cannot, which give 9p a significant advantage?
Am I correct, that 9p does not support pipelining? I suppose this would be a
big problem. For example, with http pipelining one may ask a server to HEAD
(like stat) 10,000 files together, without having to wait for the responses.
Over a high latency link (e.g. Australia -> USA), this might save perhaps an
hour of waiting.
Such an asyncronous interface might be useful even when accessing local disks -
if the filesystem receives 100 open/read/stat requests bundled together, it
might optimise disk access to minimise seeking, as is commonly done for writes.
By the way, I read the other day on this list that there is no need to improve
cat(1). Well for me, I still feel that the command `cat` without args should
concatenate 0 files (producing no output), not copy stdin to stdout!
Sam
next reply other threads:[~2010-11-15 3:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 3:25 Sam Watkins [this message]
2010-11-15 4:20 ` John Floren
2010-11-15 4:26 ` Bruce Ellis
2010-11-15 5:16 ` Sam Watkins
2010-11-15 5:26 ` John Floren
2010-11-15 14:09 ` Gorka Guardiola
2010-11-15 14:15 ` Gorka Guardiola
2010-11-15 15:37 ` roger peppe
2010-11-15 16:45 ` C H Forsyth
2010-11-15 16:37 ` roger peppe
2010-11-15 16:48 ` erik quanstrom
2010-11-15 17:02 ` roger peppe
2010-11-15 19:29 ` erik quanstrom
2010-11-15 21:38 ` roger peppe
2010-11-16 1:18 ` erik quanstrom
2010-11-16 12:12 ` roger peppe
2010-11-16 15:56 ` Charles Forsyth
2010-11-16 16:04 ` erik quanstrom
2010-11-16 16:32 ` Charles Forsyth
2010-11-16 17:11 ` roger peppe
2010-11-15 15:44 ` David Leimbach
2010-11-15 15:55 ` Venkatesh Srinivas
2010-11-15 15:57 ` David Leimbach
2010-11-15 18:44 ` Russ Cox
2010-11-15 19:00 ` Dan Adkins
2010-11-15 22:18 ` Yaroslav
2010-11-15 22:34 ` erik quanstrom
2010-11-16 12:42 ` Russ Cox
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=20101115032531.GB27578@opal.ai.ki \
--to=sam@nipl.net \
--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).