Support for application specific close codes?

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the WebSocket close-handling entry points and public API; the issue names no files or tests. Determine how close codes and reason data are currently represented, then verify that application-specific codes from 4000–4999 and the close reason can be exposed consistently across the supported targets.

Written by the indexing model from the issue text.

Description

Hi, I was wondering if there are any plans on supporting the generic application specific close codes 4000 – 4999? Also, is there a way to get the close reason data?

Dominant language
C#
Stars
1.7k
Forks
206
No merged PRs in 30d

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.

More from endel/NativeWebSocket

All issues in endel/NativeWebSocket

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.