Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Mon, 18 Jun 2001 14:29:28 -0700

> I don't know if I like it as much but what about
> beep://foo.com:<profile>:<port>:<proto>/
> This would allow us to stay near the current usages for URL's.  It has
> the disadvantage of significantly overloading the current usage for port
> specification in HTTP.
> Again I think the ugliest thing here is if we end up needing a full
> URL to identify the profile.

i'll pass. this is abstracting the wrong thing. beep isn't a protocol or a
service. it doesn't make sense to specify a url scheme for it.