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'm using multilevel with a browser client connected through websocket-stream. I've run in to the following problem: If I kill the node server (after which the client surely can no longer be connected with it) db.isOpen() still returns true and the callback to db.put is still called without an error parameter.
There seem to be no way of knowing that the connection with the server has actually disappeared. Which is not the impression the documentation gives.
I can see that there are other open issues related to disconnecting. But none of them seemed to be the exactly the same as this one.
Just in case it has any relevance I'm using level-live-stream along with multilevel.
The text was updated successfully, but these errors were encountered:
I'm using multilevel with a browser client connected through
websocket-stream
. I've run in to the following problem: If I kill the node server (after which the client surely can no longer be connected with it)db.isOpen()
still returns true and the callback todb.put
is still called without an error parameter.There seem to be no way of knowing that the connection with the server has actually disappeared. Which is not the impression the documentation gives.
I can see that there are other open issues related to disconnecting. But none of them seemed to be the exactly the same as this one.
Just in case it has any relevance I'm using
level-live-stream
along with multilevel.The text was updated successfully, but these errors were encountered: