Expose GetClientUserData
on YojimboServer class. Fix address serialization bug in matcher code.
#201
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.
Hey there. I noticed there was no method exposed for that in
yojimbo
to access the userdata inside the connection token, so I added one.I also noticed that my
userdata
bytes were "shifted" and including the trailing 12 bytes of theServerToClientKey
. After some debugging I realized that thewriteAddresses
function in the matcher code always increments the offset by 19, whether it is IPV4 or IPV6, butnetcode
it reads only as many bytes as needed. So I fixed that too.Cheers