Hi Luca,
Sorry for the delay.
If I understand correctly the pattern is:
1) ROUTER binds over TCP and enables CURVE
2) REQ connects over TCP with CURVE
3) REQ sends a message
4) REQ waits for a response that never arrives
What is the timeout value, and how is it checked (poll, socket option,
e
Well, you're right. There must be a good reason for such an undertaking.
I too feel that C++11 itself is not good enough reason.
Anyway there has to be enough people willing to contribute to it.
I was just saying this because no idea should be discarded right away, but
for sure there needs to be a
What will be the benefit from moving to C++11? And more important what is
the benefit from having two projects? one supporting C++11 and one not?
I think that maintaining two repositories is hard and not sure for what
cause?
Anyway, if some one want to do it, in the zeromq philosophy, please fork
> On May 17, 2017, at 7:56 AM, BJovke . wrote:
>
> Hello.
>
> Libzmq is not even fully C++ compliant:
> - There's no exception handling.
> - There are no RAII principles implemented.
> - Parent/child object hierarchy is loose or not implemented, all of the
> burden of proper order of cal
Hello.
Libzmq is not even fully C++ compliant:
- There's no exception handling.
- There are no RAII principles implemented.
- Parent/child object hierarchy is loose or not implemented, all of the
burden of proper order of calls is on programmer.
And so on...
C++11 is really a remarkable fe
