Initial Payload Networking API #222
Draft
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
|
I accidentally kept my glass networking HandshakePacketMixin in, I'll remove that tomorrow |
Introduce Payload class so generics are happy
Remove old code from StationConnection
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.
Making this PR to as a draft, I'll fill out this description more describing the details and impact of this tomorrow or sometime soon
Currently this PR introduces StreamCodec's to easily serialize objects
A new networking backend using nio instead of java.net (This should leave room for networking optimizations later including UDP support)
I plan to introduce a networking backend API so mods can easily register say a UDP backend for connecting to servers.
Currently connecting to servers works fine, but there is not yet a way to send custom payloads over the network yet, finding a way to do this without breaking/removing parts of the old API is very annoying and I have to account for that