- From: Mark Nottingham <mnot@akamai.com>
- Date: Tue, 21 Nov 2000 14:44:39 -0800
- To: Henrik Frystyk Nielsen <frystyk@microsoft.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. 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). On Tue, Nov 21, 2000 at 02:33:56PM -0800, Henrik Frystyk Nielsen wrote: > Ah, I see, you are talking about the request-URI so to speak - I thought > you meant "service" as in "module". > > It does make a lot of sense to have a header that knows about the XP (or > SOAP) message path model and can indicate under what conditions to send > the message to whom etc. However, I don't think it should be required as > several protocol bindings (most of the *transfer* protocols like HTTP, > SMTP etc.) have mechanisms for indicating where to send the message. > > Henrik > > > Confused - the service URI will most likely *not* be the XMLNS of the > > message/modules... > -- Mark Nottingham, Research Scientist Akamai Technologies (San Mateo, CA)
Received on Tuesday, 21 November 2000 17:45:12 UTC