From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun,  1 Jul 2007 05:15:05 -0400
From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] URI scheme for 9P2000 resources
Message-ID: <20070701091505.GZ28917@kris.home>
References: <20070701062425.GX28917@kris.home>
	<009a9ae2f5f2a8e9baaa3bd932012eb0@quintile.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="kr6QJ6xGUOmSrVQA"
Content-Disposition: inline
In-Reply-To: <009a9ae2f5f2a8e9baaa3bd932012eb0@quintile.net>
User-Agent: Mutt/1.5.15 (2007-04-06)
Topicbox-Message-UUID: 8e48326c-ead2-11e9-9d60-3106f5b1d025


--kr6QJ6xGUOmSrVQA
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 01, 2007 at 10:05:16AM +0100, Steve Simon wrote:
>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.

That's what I suggested earlier, elsewhere. The point is that it=20
has to be decided on, and universal. I'm not happy that it would=20
have a different meaning on (say) Windows, though.

9p:///tmp/ns.foo.:0/acme/1/
9p://localhost/tmp/foo
9p://plan9.bell-labs.com:wiki/installing_plan9_on_your_toaster/index.html

But my point was that any protocol other than TCP or unix would=20
seem to go unused, and break consistency with other URI types=20
(none that I know of allow you to name a protocol). If there=20
comes a time when it's a must, something (as suggested) like=20
this:

9p-il://ken/cc/

--=20
Kris Maglione

Writings prepared without understanding must fail in the
first objective of communication -- informing
the uninformed.

--kr6QJ6xGUOmSrVQA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFGh3CZseQZD8Aui4wRAnn7AJ0eRBPZqX72y2cLHLtNhij1oKsrXACgiKR5
oQNxanb/QaGH1ebyOHmVDY4=
=Rc1j
-----END PGP SIGNATURE-----

--kr6QJ6xGUOmSrVQA--