File

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.

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
}