ReconnectingWebSocket much slower than WebSocket
See original GitHub issueI have a simple app for asynchronous message passing, using websockets (React + Django).
If I use WebSocket
, the connection opens almost instantaneously upon loading the page, whereas if I switch to ReconnectingWebSocket
(that’s the only change in the code and using
import ReconnectingWebSocket from 'reconnecting-websocket';
), it takes around 3-5 seconds.
Is the reason behind this delay understood?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Slow HTTP vs Web Sockets - Resource utilization
A WebSocket and a "slow" HTTP connection both use an open connection. The difference is in expectations of the server design. Typical HTTP...
Read more >Snatchbot too slow
I am getting "reconnecting-websocket.js:231 WebSocket connection to 'wss://es.snatchbot.me/bot/ws' failed: WebSocket is closed before the connection is ...
Read more >Server-Sent Events: the alternative to WebSockets you should ...
WebSockets are the most used technology for real-time web apps. However, Server Sent Events (SSE) are a simpler alternative that is often ...
Read more >WebSocket server stops sending data to client after a time
What we typically refer to as "slow consumer", what could be happening is the "ping" messages are being sent out in the expected...
Read more >reconnecting-websocket - npm
WebSocket that will automatically reconnect if the connection is closed. Features. WebSocket API compatible (same interface, Level0 and Level2 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
it would indeed be great to have the first attempt to be immediate!
I’ve just opened a pull request here: #94