Disconnect overtakes final message

Open
#108 1 comment 1 reaction 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start by tracing the C# Send and Disconnect calls shown in the issue and how they are handled when invoked in the same tick. Reproduce the sequence with FinalMessage and verify whether the host receives it before disconnect processing; done means the final message is not dropped and ordering is preserved.

Written by the indexing model from the issue text.

Description

When I send a message and disconnect a client immediately afterwards (in the same tick) it seems like this last message is being dropped. I was wondering if the framework shouldn't make sure that no messages are lost, meaning that message and disconnect are processed in the appropriate order.

This is a simple code example in C#:

var message = new FinalMessage();
client.Send(message.Serialize());
client.Disconnect();

The FinalMessage will not arrive at the host.

Dominant language
C#
Stars
1.2k
Forks
141
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 MirrorNetworking/Telepathy

All issues in MirrorNetworking/Telepathy

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.