From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] HTTP tunnelling of 9P -- taboo?
Date: Mon, 4 Nov 2002 16:38:35 -0500 [thread overview]
Message-ID: <9ac56b3938baa3accb55d587a63f662a@9srv.net> (raw)
the aesthetic question is easiest: good God please no! tunneling
*anything* through http is ugly, since http itself is ugly. and
taking a nice, clean, simple, powerful protocol and shoving it
into an awkward dinky protocol is always aestheticaly wrong.
technically, the issue probably isn't getting around firewalls,
but proxies. firewalls generally just allow or disallow a certain
set of ports (most, anyway). if that's indeed the issue, just run
a listener on port 80 of your server and connnect to that.
also, why would a distributed fs protocol need to be embeded in
http to be an alternative to WebDAV? why not just use 9p as is?
the drive to embed everything in http seems strange to me. is
the fact that WebDAV is a set of http "extentions" really a
selling point for most of its users? i doubt it.
ア
next reply other threads:[~2002-11-04 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 21:38 a [this message]
2002-11-04 23:04 ` matt
2002-11-05 10:14 ` Boyd Roberts
2002-11-05 16:47 ` peter huang
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 22:04 Geoff Collyer
2002-11-04 19:02 Skip Tavakkolian
2002-11-04 15:44 Skip Tavakkolian
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=9ac56b3938baa3accb55d587a63f662a@9srv.net \
--to=a@9srv.net \
--cc=9fans@cse.psu.edu \
/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).