Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No indication that connection is lost #61

Open
paldepind opened this issue Nov 24, 2014 · 1 comment
Open

No indication that connection is lost #61

paldepind opened this issue Nov 24, 2014 · 1 comment

Comments

@paldepind
Copy link

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.

@juliangruber
Copy link
Owner

hey @paldepind, can you post a short gist with how you hook up the websocket-stream to the db?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants