From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b1a1c175475506f522369932bd9d0fd4@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Sat, 30 Jun 2007 08:02:09 -0400
To: weigelt@metux.de, 9fans@cse.psu.edu
Subject: Re: [9fans] URI scheme for 9P2000 resources
In-Reply-To: <20070630114754.GB9515@nibiru.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc:
Topicbox-Message-UUID: 8c931284-ead2-11e9-9d60-3106f5b1d025

> The scheme should be "9p", obviously. Where to put server name
> and port is also obvoius. So for the simple TCP case, we can
> use something like:
>
>     9p://localhost:9000/my/path
>

the format for a dial string is proto!server!port.  e.g. tcp!atlas.coraid.com!http.
going with your style this would be

	9p://tcp!localhost!service/my/path

a more regular name would be

	9p://tcp/localhost/service/my/path

(see pike's paper "the hideous name".)

but what is the point of encoding a dial string+path as a url?

- erik