Add an example of a unreliable WebSocket-like API on top of QuicTransport #107
Conversation
This file contains 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
… well as a fake QuicTransport to test with.
|
Note to self - read through this then it should be ready to submit. |
|
Note from editor's meeting: waiting for at least one person to read this |
|
Hey @pthatcherg, I went ahead and uploaded changes here. The main things are:
Might be worth looking over things again, but this is now probably in a good enough state to merge. |
|
Referencing this to issue 22 |
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.
And also a fake QuicTransport loopback object.
Not sure if everything works, but I tested many things and most seems to work.
Might be useful as proof that a high-level API on top of a low-level API can work pretty easily.