Suport for WebSocket fallback
I searched for any docs on websocket fallback but couldn't find anything.
Is there any future plan for supporting websocket fallbacks such as HTTP long-polling?
Sure, websocket is widely being used. However, there is a situation where the client is located in a network/proxy that blocks the websocket connection. Real-time libraries and frameworks such as Socket.IO, SignalR, and Phoenix LiveView implement long-polling to ensure that the client can communicate with the server without 100% relying on WebSocket.
Although the websocket blocking case is very minor, AFAIK, it does happen. Projects that greatly benefit the Convex stack might hesitate from adopting it to avoid the risk of their user being unable to access their website due to the websocket blocking.
Or is it unfeasible for Convex to support websocket fallback?
1 Reply
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!