Rolf Timmermans
Rolf Timmermans
I recently had the chance to review the implementation of this library a little. I noticed the implementation is based on event emitters, like the current version of zeromq.js. I...
You can't add backpressure if the underlying API is an event emitter, but the reverse is possible. So you can write async/await first and add an event emitter layer on...
It's been a while since you asked this, but could you elaborate what you expect from such functionality? The polling logic is integrated into the Node.js event loop and it...
Good question; the error messages are maybe a bit cryptic given that they're currently just short strings based on the `errno` received by libzmq. "Socket temporarily unavailable" / `EAGAIN` means...
Oh, and another reason for `EGAIN` is if two calls to `receive()` or two calls to `send()` are made while the first has not resolved. That's explicitly disallowed because it...
The best solution is to use `await send()`, because it will throw an error in-place, with a correct stack. I wish there was a way to disallow `send()`/`receive()` without using...
I have updated the error messages in master. Another thing I realised is that a concurrent send now returns `EAGAIN` which is probably a bad idea because that makes it...
A new beta is out; would love to hear wat you think and if you manage to pinpoint what is causing the issue you described!
Makes sense. A PR would be welcome!
Thanks for reporting! Do you have any code that reproduces this issue? Which OS are you using?