the last message before close may not be handled ?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
when a frame arrived:
if it's a data frame , it will be apended to message queue. and will be handled in message()
if it's a close frame , then close() func is called
in close() , the _readyState will be set to Closing
in message() , if _readyDtate != Open , the message queue will not be handle
in my situation, the last message is very important, so how to gurantee all messages are handled before close ?
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 tracing the data-frame and close-frame paths described in the issue, especially close() and message(), and inspect how _readyState gates message-queue handling. Reproduce a close immediately after a final data frame, then verify that the queued message is handled before the connection transitions fully closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100