lipp / lipp/lua-websockets

client:getpeername() but with websocket:client?

Open
#114 0 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

Is there an equivalent of client:getpeername() but with websocket:client?
I have a monitoring program that periodically checks for the status of this websocket connection. If it is not connected, I reconnect.
For this, I was trying to use client::getpeername() and use the return string to determine if the socket is healthy or not.
Thanks

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 inspecting the websocket:client interface and the existing client:getpeername() API mentioned in the issue. Determine whether an equivalent peer or connection-status operation is expected, then define completion as either a documented supported approach or a clearly scoped API change with coverage for the monitoring use case.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.