prosody
da154ced7de4
doc/stanza_routing.txt

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

doc/stanza_routing.txt @ 9161:da154ced7de4

util.pubsub: For open nodes, default affiliation is "member" This allows entities without an explicit affiliation to retrieve items, which is specified by the XEP. Table 6: "Node Access Models" states that for 'open' nodes, "any entity may retrieve items from the node". See also discussion at: https://mail.jabber.org/pipermail/standards/2018-August/035320.html
author Matthew Wild <mwild1@gmail.com>
date Thu, 09 Aug 2018 20:27:04 +0100
parent 22:2856dfc1f5cc
line wrap: on
line source

No 'to' attribute:
	IQ:			Pass to appropriate handler
	Presence:		Broadcast to contacts
				- if initial presence, also send out presence probes
					- if probe would be to local user, generate presence stanza for them
	Message:		Route as if it is addressed to the bare JID of the sender

To a local host:
	IQ:			Pass to appropriate handler
	Presence:		-
	Message:		Deliver to admin?

To local contact:
	Bare JID:
		IQ:		Pass to appropriate handler
		Presence:	Broadcast to all resources
		Message:	Route to 'best' resource
	Full JID:
		IQ:		Send to resource
		Presence:	Send to resource
		Message:	Send to resource
	Full JID but resource not connected:
		IQ:		Return service-unavailable
		Message:	Handle same as if to bare JID
		Presence:	Drop (unless type=subscribe[ed])

To remote contact:
	Initiate s2s connection if necessary
	Send stanza across