From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] URI scheme for 9P2000 resources
Date: Sun, 1 Jul 2007 10:05:16 +0100 [thread overview]
Message-ID: <009a9ae2f5f2a8e9baaa3bd932012eb0@quintile.net> (raw)
In-Reply-To: <20070701062425.GX28917@kris.home>
I'am no fan of URIs, however if we must have them:
> The only real problem I see here
> is that the protocol specification. It would be nice to handle unix
> domain sockets, since p9p uses them, but I think any other
> protocol would be superfluous, and should probably be part of
> the resource.
Wouldn't a heuristic be enough here? if the host specified is the localhost
then forst try to attach to a Unix domain socket, if that fails then try
an IN connection to the localhost instead, the port number would become
the socket's path.
If this where ever used on plan9 the name would (I guess) become the name in /srv
where the fd was posted.
this way we have one uniform uri [sic].
-Steve
next prev parent reply other threads:[~2007-07-01 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 11:47 Enrico Weigelt
2007-06-30 12:02 ` erik quanstrom
2007-06-30 15:32 ` David Arnold
2007-06-30 17:11 ` Enrico Weigelt
2007-06-30 17:46 ` Lyndon Nerenberg
[not found] ` <12cc024df6f0b86decfe2af2a1ab42f1@coraid.com>
2007-06-30 12:12 ` Enrico Weigelt
2007-06-30 19:34 ` erik quanstrom
2007-06-30 20:26 ` Uriel
2007-06-30 22:54 ` Skip Tavakkolian
2007-06-30 22:59 ` Kris Maglione
2007-07-01 6:13 ` Skip Tavakkolian
2007-07-01 6:24 ` Kris Maglione
2007-07-01 8:54 ` matt
2007-07-01 9:04 ` Kris Maglione
2007-07-01 9:05 ` Steve Simon [this message]
2007-07-01 9:15 ` Kris Maglione
2007-07-01 11:21 ` erik quanstrom
2007-07-01 11:11 ` 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=009a9ae2f5f2a8e9baaa3bd932012eb0@quintile.net \
--to=steve@quintile.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).