88
edits
Difference between revisions of "XMPP 2.0"
Jump to navigation
Jump to search
m
→Migration path in a hypothetical XMPP 2.0 Session: minor clarification
m (→Migration path in a hypothetical XMPP 2.0 Session: minor clarification) |
|||
| Line 43: | Line 43: | ||
* A stanza with a <code><xmpp-2/></code> tag MUST be processed as if it came from an XMPP 2.0 node. Any XMPP 1.0 Routing Modifiers MUST be stripped. | * A stanza with a <code><xmpp-2/></code> tag MUST be processed as if it came from an XMPP 2.0 node. Any XMPP 1.0 Routing Modifiers MUST be stripped. | ||
* A message to a ''bare JID'' must be delivered to all online clients (this is allowed by RFC 6120 already). | * A message to a ''bare JID'' must be delivered to all online clients (this is allowed by RFC 6120 already). | ||
* A message to a ''full JID'' with <code><private/></code> or <code><no-copy/></code> is delivered to the targeted full JID (this matches current Carbons behavior). | * A message to a ''full JID'' with <code><private/></code> or <code><no-copy/></code> is delivered only to the targeted full JID (this matches current Carbons behavior). | ||
* For a message to a ''full JID'' with no XMPP 1.0 Routing Modifier, a set of rules similar to Carbon copying needs to be applied, to determine if the message must be rerouted to the bare JID: | * For a message to a ''full JID'' with no XMPP 1.0 Routing Modifier, a set of rules similar to Carbon copying needs to be applied, to determine if the message must be rerouted to the bare JID: | ||
** type=normal - needs to detect body presence / special use cases | ** type=normal - needs to detect body presence / special use cases | ||