From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] plan9port: tcp servers
Date: Sun, 1 Jun 2008 11:04:38 -0500 [thread overview]
Message-ID: <a4e6962a0806010904l6d09aa9fu51f205608adfa9c0@mail.gmail.com> (raw)
In-Reply-To: <42b189b6ce70d1edc9060fdc96e698b4@quanstro.net>
On Sun, Jun 1, 2008 at 10:41 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> 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.
>
Why include the tcp path element? Name resolution should be able to
determine the best network path to the service.
-eric
next prev parent reply other threads:[~2008-06-01 16:04 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
2008-06-01 16:04 ` Eric Van Hensbergen [this message]
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=a4e6962a0806010904l6d09aa9fu51f205608adfa9c0@mail.gmail.com \
--to=ericvh@gmail.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).