From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] URI scheme for 9P2000 resources
Date: Sat, 30 Jun 2007 19:11:32 +0200 [thread overview]
Message-ID: <20070630171132.GA1435@nibiru.local> (raw)
In-Reply-To: <200706301532.l5UFWXTC024201@laika.gnusto.com>
* David Arnold <davida@pobox.com> wrote:
> the relevant specification is RFC-3986, and especially section 3.
>
> SLP (RFC-2608) gives an example of existing practice using a form like
>
> 9p:tcp://hostname/service/my/path
hmm, is this an valid URL ?
> Subversion uses
>
> svn+ssh://hostname/my/path
Seems some bit unclean to me, if we would put the transport proto
here. It should be as optional as the port. inetd-style port notation
(ie. 123/tcp) could be nice, but would be incompatible.
Why not
9p:/proto/hostname:port/my/path
or
9p://hostname:port.proto/my/path
?
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next prev parent reply other threads:[~2007-06-30 17:11 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 [this message]
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
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=20070630171132.GA1435@nibiru.local \
--to=weigelt@metux.de \
--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).