From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 1 Jul 2007 02:24:25 -0400 From: Kris Maglione To: 9fans@cse.psu.edu Subject: Re: [9fans] URI scheme for 9P2000 resources Message-ID: <20070701062425.GX28917@kris.home> References: <5d375e920706301326j6efe8921td46d6958299eef62@mail.gmail.com> <20070630225955.GW28917@kris.home> <84d462a30706302313r5bf288c9l43d02fd9b031ddbd@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hblleJHDxiLJUoyx" Content-Disposition: inline In-Reply-To: <84d462a30706302313r5bf288c9l43d02fd9b031ddbd@mail.gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) Topicbox-Message-UUID: 8d98b5e4-ead2-11e9-9d60-3106f5b1d025 --hblleJHDxiLJUoyx Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 30, 2007 at 11:13:23PM -0700, Skip Tavakkolian wrote: > if it handles 9p: scheme, it better be 9p, not some dialect based > on implementer's (mis)understanding of it. browser plugins, by virtue of > what they plug into, have a potential to spread fast. it will not serve > anyone if a popular derivation becomes a de facto standard for 9p. While I'd generally be the first to argue such a point, I don't=20 see where you see a problem. It should act exactly the same as=20 file:, ftp:, http:, smb:, ... The URI format just describes the=20 location of a resource. The resource should be handled exactly=20 the same as any other resource. The only real problem I see here=20 is that the protocol specification. It would be nice to handle unix=20 domain sockets, since p9p uses them, but I think any other=20 protocol would be superfluous, and should probably be part of=20 the resource. --=20 Kris Maglione The meek shall inherit the earth, but not its mineral rights. --hblleJHDxiLJUoyx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGh0iZseQZD8Aui4wRAmkeAJ0euQmolZ4EtFfzLLskAZw23jXe+wCfUqhU Pi7lkl5D/bn1HEwxsNMkgpE= =xjPX -----END PGP SIGNATURE----- --hblleJHDxiLJUoyx--