-
Notifications
You must be signed in to change notification settings - Fork 1
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
Server 'closed' event never emitted #7
Comments
@tehnorm Thanks for the report! Glad the package is useful :) I'm traveling today, but I will check it out as soon as I can. How would you feel about me generally supporting the |
@crussell52, thanks for the quick response! No worries - it is the travel season. For now, I'm just listening to the |
`closed` event is now emitted, but also deprecated in favor of more familiar `close` event. For now, both will be emitted, in `v1.0.0` the `closed` event will be removed.
Server 'closed' event documented but never emitted (#7)
Should be fixed in |
Thanks @crussell52 |
@tehnorm no worries. Just heads up. |
I appreciate you writing this lib - it really fits the bill for our use case for domain socket communication in node.
Had a server hang on me when trying to call
Server.close()
and listening for theclosed
event to confirm shutdown. After some digging it looks like a possible typo:https://github.com/crussell52/node-socket-ipc/blob/master/src/index.js#L231
Should this emit a
closed
event to match the API docs? Currently aclose
event is being emitted. Good-ole missing one character bugs!The text was updated successfully, but these errors were encountered: