W3C home > Mailing lists > Public > uri@w3.org > June 2001

Re: fyi: should URIs convey protocol/service layering?

From: Michael Mealling <michaelm@neonym.net>
Date: Fri, 15 Jun 2001 12:49:14 -0400
To: Dan Connolly <connolly@w3.org>
Cc: uri@w3.org
Message-ID: <20010615124914.F12140@bailey.dscga.com>
On Fri, Jun 15, 2001 at 11:41:21AM -0500, Dan Connolly wrote:
> Jeff.Hodges@kingsmountain.com wrote:
> > This is a couple'o (key) messages from a thread over on the
> > bxxpwg@invisible.net list that may be of interest to folks here.
> Thanks for bringing it up here; this is an issue folks
> have been noodling on for years:
> <snip>references to articles on methods for doing it</snip>
> I hope to find time to study the practical details
> of the design you're discussing. But for now,
> I hope the historical pointers are useful/interesting...

This has also come up in a few other places. The one that was the most
practical was in CNRP where we were also layering some XML over
some transport (smtp, http and some UDP transport were the most popular).

We came up with two solutions and picked the easiest one (#2) for now:

Solution 1) Use NAPTR to map between a protocol independnet URI and
the transport dependent one.

Solution 2) Encode the transport information in a service description object
and then specify one of the transports as mandatory to implement but only
require that it be able to publish those service description objects.

Solution 1 can be considered a specific case of solution 2. The general
case is creating some common rendesvous point where the transport
information is discovered....


Michael Mealling	|      Vote Libertarian!       | urn:pin:1
michael@neonym.net      |                              | http://www.neonym.net
                        |                              | go:Michael Mealling
Received on Friday, 15 June 2001 12:53:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:03 UTC