You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only single frame messages can be processed by the WebSocket Gateway. Fragmentation of frames is not implemented.
This should be changed with this feature.
"""
A fragmented message consists of a single frame with the FIN bit clear and an opcode other than 0, followed by zero or more frames with the FIN bit clear and the opcode set to 0, and terminated by a single frame with the FIN bit set and an opcode of 0.
"""
The text was updated successfully, but these errors were encountered:
SmySmy
pushed a commit
to SmySmy/OpcUaWebServer
that referenced
this issue
Nov 7, 2022
Currently, only single frame messages can be processed by the WebSocket Gateway. Fragmentation of frames is not implemented.
This should be changed with this feature.
This feature should implements the fragmentation for text frames. This process is defined in https://www.rfc-editor.org/rfc/rfc6455#section-5.4
"""
A fragmented message consists of a single frame with the FIN bit clear and an opcode other than 0, followed by zero or more frames with the FIN bit clear and the opcode set to 0, and terminated by a single frame with the FIN bit set and an opcode of 0.
"""
The text was updated successfully, but these errors were encountered: