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.

Sign up for GitHub

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

Jump to bottom

Handle the case when the socket is disconnected by the server #16

Closed
kadishmal opened this issue Jan 30, 2015 · 1 comment
Closed

Handle the case when the socket is disconnected by the server #16

kadishmal opened this issue Jan 30, 2015 · 1 comment
Labels
enhancement
Milestone
v2.1.1

Comments

@kadishmal
Copy link
Contributor

Migrated from http://jira.cubrid.org/browse/APIS-690.

Once in a while clients may lose the connection to a CUBRID server due to network problems, the server timing out, the server being restarted, or crashing. All of these events should be handled and should flag the current connection is closed. Optionally if there are any listeners for the "disconnect" event, we can emit the notification.
@kadishmal kadishmal added this to the 2.1.1 milestone Jan 30, 2015
@kadishmal
Copy link
Contributor Author

Improved in v2.1.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
v2.1.1
Development

No branches or pull requests
1 participant
@kadishmal