How do WebSocketBehaviors work with a WebSocketServer?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hello @sta -
Thanks for the great library! I'm having trouble understanding how WebSocketBehaviors work for a WebSocketServer.
Is there a new instance of the WebSocketBehavior instantiated for every new connection made to the server?
I'm trying to use a WebSocketBehavior to manage all connected clients and I'm getting duplicated messaging.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the WebSocketBehavior and WebSocketServer documentation or implementation to determine the behavior instance lifecycle for connections. Document that lifecycle and clarify the correct way to manage connected clients without duplicated messaging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100