lipp / lipp/lua-websockets

New backend

Open
#49 7 comments 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

I just imlement new [backend for lua-websocket](https://github.com/moteus/lua-websockets-lluv) based on [my libuv binding](https://github.com/moteus/lua-lluv).
For now it implement same API as `ev` backend.
And I have several question:
1 To be avaliable you need add optional require to client/server files in main repo? (I have no objection to just merge my reto to this repo)
2 No all Linstners share same client set (`clients` table). Is it intentional or better if each server will have its own set?
3 To support `wss` protocol is it enough just make TLS connection?

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 reviewing the existing `ev` backend and the client/server files referenced in the issue. Resolve how the optional backend is exposed, whether listener client sets are shared intentionally, and what `wss` requires; the work is done when the new backend's integration and behavior are agreed and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
backend, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.