Wire stateless native admission into the Geyser provider factory - #2
Merged
Conversation
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
1 participant
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.
Provider mode can now open the fixed-UDP native Warden endpoint through the existing factory SPI and retain Geyser's Bedrock child pipeline. The factory loads a pre-provisioned PEM identity; the transport receives background host keys/profile state and admits clients from the authenticated STUN token plus integrity. No per-join offer/control delivery is added.
Stacked on #1 (
codex/registration-provider). Native transport dependency is teamziax/NetworkCompatible#1; generic provider dependency is teamziax/NetworkCompatible#2.scripts/build-native-development.shcomposes both exact source pins in a disposable local checkout, runs their tests and builds the extension without merging or pushing either source branch. The artifact manifest records the extension, provider, native and JNI revisions.Validation at
c3a07a6efdd87928d9bdaa69ccbd2c156ac97607: CI 33831965646 passes C++ teardown regressions, 167/178/256-character native token probes, wrong-fingerprint DTLS rejection, provider/native Java tests, extension build/tests and shaded service/native-library checks. The real Worker plus isolated native host/client bench in teamziax/warden-signalling#7 passes both-channel echo with all per-join control inserts forbidden and two-host routing with fixture registration.Experimental Linux x86_64 classifier links system OpenSSL. Requires an explicit bound interface/candidate and pre-provisioned host-cert.pem / host-key.pem; wildcard/NAT advertised-address configuration is not supported yet. Stock-client admission, gameplay, stock two-host routing and a refreshed direct-join regression remain unproven. Keep this draft open for those gates; no merge or deployment requested.