Add support for custom Bedrock transports#6488
Open
irrld wants to merge 1 commit into
Open
Conversation
irrld
force-pushed
the
master
branch
2 times, most recently
from
6c14079 to
07e1fae
Compare
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.
The goal of this pull request to add a way for extensions to create their own transport layers (such as TCP or QUIC) for more efficient transport. This is useful when running Geyser behind a proxy like WaterdogPE where the connection between Geyser instance and WDPE is in our control, using RakNet is less efficient in use cases like these.