File

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.

Structure of a stanza:


stanza {
	--- properties ---
	tags -- array of tags
	
	--- static methods ---
	iq(attrs) -- 
	
	--- read-only methods ---
	reply -- return new stanza with attributes of current stanza
	child_with_name(string name) -- return the first child of the current tag with the matching name
	
	--- write methods ---
	tag(name, sttrs) -- create a new child of the current tag, and set the child as current
	up() -- move to the parent of the current tag
	text(string) -- append a new text node to the current tag
}