Received message by server is kept in memory. How to clear?

Open
#115 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Reproduce the two-message sequence using the Unity server setup described in the issue and compare the received strings. No source file or test is named; trace the server's message-receiving path and consider the issue resolved when successive messages no longer retain text from the earlier message.

Written by the indexing model from the issue text.

Description

I have a Server receiving messages from a client in Unity, setup like the example in the wiki.
I am sending two different messages on two different key presses, one on space bar press and the other on Q key press.
The message on space bar press is longer than the message on Q press.

Space bar message, server receives: "Client sends message on Space key press."
Q key message, server receives: "Beep beep beep on Q key press!"

If I press space bar first, and send the above message, and then press on Q, the server receives:
"Beep beep beep on Q key press!key press.", which shows that the previous message, sent on space bar was not cleared.
Is this a defect? How do you clear previous messages if not a defect?

Thank you.

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.