Skip to content

Build Frame From Buffer #7

@CodyNault

Description

@CodyNault

!!-----I marked this as invalid because it recently occurred to me that we shouldn't try to package the frame payloads into a single buffer but it should really work as a stream so we can deal with large payloads without loading them all into memory I will update this issue shortly----!!!

Currently the TCP listener is set up to perform the websocket HTTP handshake and it now needs to parse the frame transmission.

Currently we have a factory method called WebSocket_Frame::buildFrameFromBuffer that needs to parse the raw binary buffer containing the websocket frame.

Read section 5 on Data Framing in the RFC https://tools.ietf.org/html/rfc6455 to understand how the frame works.

You will need to setup other getters and setters for the WebSocket_Frame object, currently we only have setStringPayload and getStringPayload that is designed to set and get a string object version of the payload data after unmasking.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions