From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9port: tcp servers
Date: Sun, 1 Jun 2008 11:41:37 -0400 [thread overview]
Message-ID: <42b189b6ce70d1edc9060fdc96e698b4@quanstro.net> (raw)
In-Reply-To: <20080601142556.C91931E8C1F@holo.morphisms.net>
the fact that dial strings live in their own parallel
universe has always seemed un-plan 9-ish to me.
> network addresses and files are different kinds of names.
> mixing them would introduce ambiguities, like what
> if i have a file name 'tcp!bell-labs.com!http'.
we don't have this problem with devices, due to convention.
if we didn't have an implicit /net, i don't think your example
would lead to any confusion.
/net/tcp!bell-labs.com!http
is pretty clearly not a normal file.
on the other hand, making dial strings special, cuts the
namespace out of how network names are constructed.
you can't create a special case in networking with bind(1).
> also there was no obvious error response if you
> dial "a!b!c!d!e". is it a malformed address?
> not if a file name a!b!c!d!e exists. but in general, yes.
if dial strings are written with / and not !
/net/tcp/bell-labs.com/http,
an appropriately constructed namespace could
allow the "correct" fileserver to pass judgement.
- erik
next prev parent reply other threads:[~2008-06-01 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 12:35 Enrico Weigelt
2008-05-27 14:44 ` Russ Cox
2008-06-01 10:45 ` Enrico Weigelt
2008-06-01 13:00 ` Russ Cox
2008-06-01 13:28 ` Enrico Weigelt
2008-06-01 14:26 ` Russ Cox
2008-06-01 15:41 ` erik quanstrom [this message]
2008-06-01 16:04 ` Eric Van Hensbergen
2008-06-04 3:23 ` erik quanstrom
2008-06-05 11:08 ` Enrico Weigelt
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=42b189b6ce70d1edc9060fdc96e698b4@quanstro.net \
--to=quanstro@quanstro.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).