You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to ask, how can I solve reconnecting issue using this library. Or should I do connect every time I want to make a call? That doesn't really make a sense when websockets are involved. When a server goes down, I'd expect a websocket to try to reconnect, or am I wrong?
The text was updated successfully, but these errors were encountered:
@jvorcak This library is currently intended to provide the same API as the official rethinkdb javascript driver, identical except using a websocket instead of a TCP socket.
For something higher level that manages automatic reconnecting, something like react-rethinkdb can manage automatic reconnection. Or any other high level data layer library could sub rethinkdb-websocket-client in place of the rethinkdb driver.
Does that make sense, or is there a reason you think automatic reconnection should be implemented at this level?
Web sockets normally timeout after 300 seconds to close idle connections. The reconnect option seems to be a natural solution. The reconnect should be lazy. In other word only when a query needs to run with a closed out connection.
Hi,
I'd like to ask, how can I solve reconnecting issue using this library. Or should I do connect every time I want to make a call? That doesn't really make a sense when websockets are involved. When a server goes down, I'd expect a websocket to try to reconnect, or am I wrong?
The text was updated successfully, but these errors were encountered: