lipp / lipp/lua-websockets

Reserve `websocket.extension` name

Open
#89 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
419
Forks
117
PR merge metrics
No merged PRs in 30d

Description

Hello. I write extension plugin manager for [websocket](https://github.com/moteus/lua-websockets-extensions) and permessage-deflate extension. I test it with my websocket implementation and it pass all AutoBahn tests (client and server).
I name it like `websocket.extensions`. In fact this module does not do any IO it just encode and decode already readed data and tell what need to add to handshake.
So I think it should be not difficult to add support extensions to your implementation.
You need just add ability to add headers to handshake to add `Sec-Websocket-Extensions` header.
And encode/decode RSV bits.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the websocket handshake and frame encoding/decoding paths in the repository. The issue describes adding the Sec-Websocket-Extensions handshake header and handling RSV bits for extension encode/decode. Done means an extension manager such as permessage-deflate can integrate without breaking existing websocket behavior; no tests or file paths are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.