Re: [9fans] URI scheme for 9P2000 resources

[Kris Maglione <bsdaemon@comcast.net>]

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

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 
has to be decided on, and universal. I'm not happy that it would 
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 
seem to go unused, and break consistency with other URI types 
(none that I know of allow you to name a protocol). If there 
comes a time when it's a must, something (as suggested) like 
this:

9p-il://ken/cc/

-- 
Kris Maglione

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

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]