fix(websockets): unable to send messages to clients #115
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
Now that each `cloud.Function` executes in it's own process, it is impossible to use a global WebSockets server to send messages. Instead, starts a small local http server that sends the messages across process boundaries.
ekeren
reviewed
Mar 12, 2024
ekeren
approved these changes
Mar 12, 2024
|
Thanks for contributing, @eladb! This PR will now be added to the merge queue, or immediately merged if |
5 tasks
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.
Now that each
cloud.Functionexecutes in it's own process, it is impossible to use a global WebSockets server to send messages.Instead, starts a small local http server that sends the messages across process boundaries.