OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bt-messaging message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: MESSAGING STRAWMAN [1 of 5] Addressing



ADDRESSING

<some-address>
	<carrier>btp:btp-soapbinding-v1</carrier>
    <carrier-address>carrier specific URI</carrier-address>
    <additional-information>...optional additional addressing
information...</additional-information>
</some-address>



<some-address>

<carrier-address>http://www.example.com/Servlet/BTP/dispatch?coordinator=123
45</carrier-address>
</some-address>

In the above address, the URI in carrier-address is sufficient to route the
message.



<some-address>
    <carrier-address>mailto:btp@example.com</carrier-address>
    <additional-address>coordinator:12345</additional-address>
</some-address>

In the above address, the URI in carrier-address is not sufficient to route
the message and so an additional-address exists.



Issue[MSG_001]: is this what was envisaged?
	Yes
	All carrier addresses will be URIs (for our defined bindings)
	additional information is useful, and so calledg

MSG_005: address includes carrier binding identification - including
possible versions of bindings.

A "published" address can be a set of <some-address>, which are alternatives
one of which is chosen by the peer (sender)



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC