ValveSoftware / ValveSoftware/GameNetworkingSockets
API to disable retry for reliable messages (outdated messages)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.9k
- Forks
- 749
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
I want to implement a data replication system where data is one way replicated from server to client. Replicating data like unit positions should be reliable, while occasional data loss is acceptable. So whenever a new replication message is sent, older messages will no longer perform retransmission. (The last message will need to be reliable so the unit won't stay at wrong places on clients).
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 reviewing the existing reliable-message API and how retransmission is handled for messages that become outdated. Define how newer replication messages supersede older ones while the latest message remains reliable. Done means the API supports this behavior without leaving the client at an incorrect final state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100