It's easier to think about ZeroMQ as the community and libzmq as the
messaging library.  I believe that's how Pieter was describing ZeroMQ
at the end.

-Trev

On Mon, Apr 1, 2019 at 2:45 PM Michal Vyskocil
<[email protected]> wrote:
>
> Hi,
>
> Don't worry, it is confusing.
>
> If you built from zeromq tarball, then you have libzmq, the original zeromq 
> engine written in C++. That's why I wrote that zeromq equals libzmq in your 
> case. I don't know about others implementations (like jeromq, engine written 
> in Java), but I would say that libzmq is the most feature complete and most 
> used engine so far.
>
> Dne po 1. 4. 2019 20:19 uživatel jonetsu <[email protected]> napsal:
>>
>> On Mon, 1 Apr 2019 20:00:20 +0200
>> Michal Vyskocil <[email protected]> wrote:
>>
>> Hi,
>>
>> > However libzmq equals to zeromq for you. See release page
>> > https://github.com/zeromq/libzmq/releases tarballs are named zeromq.
>> > That's more the historical coincidence.
>> >
>> > Nowadays zeromq is the project umbrella and libzmq is the C++ engine
>> > implementing the zmtp and other protocols.
>> >
>> > Btw: I would personally use https://github.com/zeromq/czmq/ than
>> > cppzmq. Czmq is very active project, which offer great C API built on
>> > top of libzmq. Plus a lot more like actor model, configuration files
>> > parsing, curve support via zauth and many more.
>>
>> Thanks !  However, please bear with me on this as it's still not
>> obvious and I have to ask: is libzmq implementing features (zmtp, other
>> protocols) not found in the umbrella zeromq that I've built ?
>>
>> libzmq could be more what I'm looking to use as a base, since I'm going
>> C++, so there would be a difference between it and the umbrella...
>>
>> Cheers.
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to