feat(csharp): migrate to VSR wire protocol - #3800
Open
lukaszzborek wants to merge 14 commits into
Open
Conversation
lukaszzborek
force-pushed
the
dotnet-vsr
branch
from
August 2, 2026 13:44
6aded83 to
098959f
Compare
lukaszzborek
force-pushed
the
dotnet-vsr
branch
from
August 2, 2026 13:55
098959f to
e948728
Compare
numinnex
previously approved these changes
Aug 6, 2026
spetz
previously approved these changes
Aug 7, 2026
Contributor
|
please remove |
# Conflicts: # .github/workflows/_test_bdd.yml # .github/workflows/_test_examples.yml # bdd/docker-compose.vsr.yml # scripts/run-bdd-tests.sh
…bnets and simplify node address resolution
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The .NET SDK previously spoke classic TCP framing, which the clustered
next-generation server does not understand. Classic framing is now
dropped entirely: the SDK speaks VSR framing only, so every connection
goes through the register handshake, with session lifetime tied to the
connection, request sequencing, bounded reply decoding, transient
replays, leader redirection over the cluster roster, and
assignment-based consumer groups.
The IIggyClient surface is unchanged. Partitioning moves client-side
(balanced and message-key, hash byte-compatible with the Rust SDK),
credentials are bounds-checked before framing, and a request written
without a server verdict surfaces as VsrRequestOutcomeUnknownException
rather than being silently replayed on a new session, since that would
bypass server-side deduplication.