Tighter Tardy Integration #11
Merged
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
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.
This changes zzz in a pretty significant way, increasing the reliance on the Tardy runtime. This will allow for multiple clients and or servers to run on a single runtime in the future! (Work is currently being done on this in the
clientbranch to bring a Tardy compliant HTTP Client to zzz).This PR also allows for HTTP handlers to run within an asynchronous context, allowing for any requests that happen within your handler to be non-blocking. This should provide massive performance gains when making DB or HTTP calls within your handler as clients for these are developed.
This also provides a pretty crude SSE implementation that will likely be updated and refactored in a future update. It serves as a proof of concept of how Tardy Channels can be used in an application.