File

spec/scansion/keep_full_sub_req.scs @ 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 10515:35bf3b80480f
line wrap: on
line source

# server MUST keep a record of the complete presence stanza comprising the subscription request (#689)

[Client] Alice
	jid: pars-a@localhost
	password: password

[Client] Bob
	jid: pars-b@localhost
	password: password

[Client] Bob's phone
	jid: pars-b@localhost/phone
	password: password

---------

Alice connects

Alice sends:
	<presence to="${Bob's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Alice disconnects

Bob connects

Bob sends:
	<presence/>

Bob receives:
	<presence from="${Bob's full JID}"/>

Bob receives:
	<presence from="${Alice's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Bob disconnects

# Works if they reconnect too

Bob's phone connects

Bob's phone sends:
	<presence/>

Bob's phone receives:
	<presence from="${Bob's phone's full JID}"/>


Bob's phone receives:
	<presence from="${Alice's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Bob's phone disconnects