Document the Long-Poll Transport Limitations #6057
Merged
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.
Currently, Phoenix will automatically enable a long-poll Socket implementation and LiveView will fallback to long-polling automatically, in order to avoid issues with network conditions not allowing WebSockets. This comes with a major undocumented footgun - Long-Polling requires that either all requests go to the same machine (stickiness), or that nodes in a cluster can communicate.
This documents the footgun and warns the user, along with explaining why this happens.