Software /
code /
prosody
File
spec/scansion/issue1121.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 | 12100:0b14b541fd27 |
line wrap: on
line source
# When removing roster contact, Prosody should send directed "unavailable" presence but sends global unavailable presence [Client] Romeo jid: romeo@localhost password: password [Client] Juliet jid: juliet@localhost password: password ----- Romeo connects Romeo sends <presence/> Romeo receives <presence from="${Romeo's full JID}"/> Juliet connects Juliet sends <presence/> Juliet receives <presence from="${Juliet's full JID}"/> Romeo sends <presence to="juliet@localhost" type="subscribe"/> Romeo receives <presence from="juliet@localhost" to="romeo@localhost"/> Juliet receives <presence from="romeo@localhost" to="juliet@localhost" type="subscribe"/> Juliet sends <presence to="romeo@localhost" type="subscribed"/> Romeo receives <presence from="${Juliet's full JID}" to="romeo@localhost"/> Juliet sends <presence to="romeo@localhost" type="subscribe"/> Juliet receives <presence from="romeo@localhost" to="juliet@localhost"/> Romeo receives <presence from="juliet@localhost" to="romeo@localhost" type="subscribe"/> Romeo sends <presence to="juliet@localhost" type="subscribed"/> Juliet receives <presence from="${Romeo's full JID}" to="juliet@localhost"/> Romeo receives <presence from="${Juliet's full JID}" to="romeo@localhost"/> Juliet sends <iq type="set" id="iq1"> <query xmlns="jabber:iq:roster"> <item jid="romeo@localhost" subscription="remove"/> </query> </iq> Juliet receives <iq type="result" id="iq1"/> Romeo receives <presence from="${Juliet's full JID}" to="romeo@localhost" type="unavailable"/> Romeo disconnects