File

doc/stanza_routing.txt @ 12480:7e9ebdc75ce4

net: isolate LuaSec-specifics For this, various accessor functions are now provided directly on the sockets, which reach down into the LuaSec implementation to obtain the information. While this may seem of little gain at first, it hides the implementation detail of the LuaSec+LuaSocket combination that the actual socket and the TLS layer are separate objects. The net gain here is that an alternative implementation does not have to emulate that specific implementation detail and "only" has to expose LuaSec-compatible data structures on the new functions.
author Jonas Schäfer <jonas@wielicki.name>
date Wed, 27 Apr 2022 17:44:14 +0200
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