W3C home > Mailing lists > Public > xml-dist-app@w3.org > November 2000

RE: XP Service URIs

From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
Date: Wed, 22 Nov 2000 06:44:47 -0800
Message-ID: <002e01c05492$c6d77020$6701a8c0@redmond.corp.microsoft.com>
To: "Mark Nottingham" <mnot@akamai.com>
Cc: <rden@loc.gov>, "XML Distributed Applications List" <xml-dist-app@w3.org>
> Hmm. Perhaps then it should be a requirement for the protocol
> binding to
> provide a way to determine the request-URI; if there isn't
> one inherent, it
> must be transferred in the envelope.

I think it is a good idea to require that a protocol binding describes exactly
how the request-URI can be determined including if it is required to be
carried within the envelope. In many cases, it is obvious where to find it but
there might be more tricky cases like multicast addresses etc.

That there must be a request-URI somewhere I think falls out of building
a protocol in the first place - the purpose of a protocol is exactly to
exchange data and in order to do that one has to describe at least the
destination of the data.

> Modules which need
> greater confidence
> in the URI should specify that it be transferred in the envelope in a
> pre-arranged fashion (ideally, once for all modules, not once
> per module).

Yes, it is always possible to enforce information to be carried within
the XP envelope by using the optional/mandatory flag indicator that we
have a requirement for.

Henrik
Received on Wednesday, 22 November 2000 09:45:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:57 GMT