refactor(workerd): replace websocket with worker rpc #141
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
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
hi-ogawa
force-pushed
the
feat-workerd-rpc
branch
2 times, most recently
from
874cce1 to
62a4b5c
Compare
hi-ogawa
force-pushed
the
feat-workerd-rpc
branch
from
1198d73 to
e47346b
Compare
hi-ogawa
changed the title
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.
We probably don't even need websocket since service binding + rpc can make bidirectional communication easily.
(Also even if there's no rpc out-of-the-box, we can do the same from
fetchwith special endpoint like/__rpc).