W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2006

Re: ISSUE: Rewriting of destinations

From: David Hull <dmh@tibco.com>
Date: Fri, 01 Sep 2006 15:04:31 -0400
To: xml-dist-app@w3.org
Message-id: <44F8843F.4090404@tibco.com>
As it turns out, Jabber chat rooms rewrite /both/ sender and destination
[1].  The sender sends a message from its full JID to the room
(strictly, either the room's JID or the receiver's Room JID).  The
receiver gets a message from the room (strictly, the room's JID or the
sender's Room JID) to its full JID.

As usual, this is the result of decoupling and nothing to do with
multicast.  The rewriting happens both for unicast (type="chat") and
multicast (type="groupchat").

This also points out that the present text is not explicit about what
constitutes a message for comparison purposes.  The current text implies
that the sender and destination are considered, as well as the
inbound/outbound message properties.

Proposed text:

    * Change the second sentence of the first paragraph of section 2.2
      to read (as previously suggested [2])

The scope of a one-way MEP is limited to transmission of identical
messages from one sending node to zero or more receiving SOAP node(s).

    * In addition, insert the following sentences to the end of the
      second paragraph of section 2.2 (i.e., the one after the ed note),
      to clarify what "identical" means above and to call out rewriting
      of source and destination:

In normal operation, the InboundMessage property at a receiver will be
identical to the OutboundMessage at the sender.  However, sender and
receiver MAY differ in the values of the ImmediateSender and
ImmediateDestination properties, due to forwarding or similar processing
in transit.

[1] http://www.jabber.org/jeps/jep-0045.html
[2] http://lists.w3.org/Archives/Public/xml-dist-app/2006Aug/0046.html
Received on Friday, 1 September 2006 19:04:44 GMT

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