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?
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?
Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.
15,138Members
Resources
Similar Threads
Was this page helpful?
