doc/stanza_routing.txt

Fri, 20 Nov 2009 04:39:54 +0000

author
Matthew Wild <mwild1@gmail.com>
date
Fri, 20 Nov 2009 04:39:54 +0000
changeset 2089
fdd7280c4621
parent 22
2856dfc1f5cc
permissions
-rw-r--r--

s2smanager: Queue db:verify unless we already sent a db:result (if we had then it can could a dialback deadlock). Also remove some redundant code which could cause a db:result to be sent while still negotiating features (e.g. TLS) and break things. Collectively these fix a 'random' s2s failure (usually with ejabberd for some reason) - resulting in an 'unbound prefix' XML error, or 'ssl handshake failure'. Was this commit message long enough? I think so.

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

mercurial