Message size different .NET 3.5 to 4.x
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I am using websocket-sharp in unity, and when I switch to .NET 4.x, or I make a build, the incoming messages are a different size than they in the editor set to .NET 3.5
In the editor under .NET 3.5 the message is 28 bytes, this is correct. I am sending a specific set of bytes from node.js and I expect it to be 28 bytes exactly.
But if I set the editor to .NET 4.x, or I make a build even with .NET 3.5, out of either Unity 2018.1 or 2017.3, the message size grows to be 37 to 42 bytes.
Any ideas here would be appreciated, I'm at a bit of a loss figuring out why.
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
Reproduce the report in Unity 2017.3 or 2018.1 using the .NET 3.5 and .NET 4.x settings, including a build, and send the stated byte sequence from node.js. Compare the received lengths and inspect websocket-sharp's message handling; done means explaining the 37–42-byte result or restoring the expected 28-byte message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, node.js, unity
- Domain
- game-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100