Skip to content

Support RFC 7395 (WebSocket) framing#397

Merged
prefiks merged 1 commit intoprocessone:developfrom
weiss:feature/websocket-framing
Jul 27, 2022
Merged

Support RFC 7395 (WebSocket) framing#397
prefiks merged 1 commit intoprocessone:developfrom
weiss:feature/websocket-framing

Conversation

@weiss
Copy link
Copy Markdown
Member

@weiss weiss commented Jul 27, 2022

Support WebSocket framing as per RFC 7385 for opening and closing the stream.

This behavior is only enabled if <jabber type="connect" version="websocket" [...]/> is specified. Enabling it by default for WebSocket connections would require more changes to the code, which currently has a strict separation of the transport vs. application layers, with no access to the state of the other layer.

Resolves #164.

If '<jabber type="connect" version="websocket" [...]/>' is specified,
use RFC 7395 framing for opening and closing the stream.

Resolves processone#164.
@guusdk
Copy link
Copy Markdown

guusdk commented Jul 27, 2022

I have tested this change with good results: it now becomes possible to have XMPP interaction over websockets.

There are optimisations possible, but the change as-is removes an impossibility.

@prefiks prefiks merged commit cb3db05 into processone:develop Jul 27, 2022
@weiss weiss deleted the feature/websocket-framing branch July 27, 2022 18:08
@nniclausse nniclausse added this to the 1.8.0 milestone Feb 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support <open>,<close> frames with XMPP+websocket

4 participants