File

doc/stanza_routing.txt @ 12960:31b22cc221b5

mod_pubsub, mod_pep: Support per-node configurable inclusion of publisher This matches ejabberd's behaviour, using the 'pubsub#itemreply' config option. Although the current definition of this option in the specification is not as clear as it could be, I think matching what existing deployments do is the best option to resolve the ambiguity and reduce fragmentation. We should update the spec to be clearer about how to use and interpret this option. The 'expose_publisher' option for mod_pubsub is now an override (always expose or never expose). If unset, it will use the per-node config (which defaults to not exposing). Thanks to Link Mauve, edhelas and goffi for sparking this feature.
author Matthew Wild <mwild1@gmail.com>
date Wed, 22 Mar 2023 11:39:19 +0000
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