Oh indeed. It's not much in CZMQ either (a little portability shim to get Windows to cooperate). The work is in creating the pipe and passing contexts and such.
However once you have that attached thread abstraction you can do useful things with it. On Tue, Mar 11, 2014 at 10:33 PM, Lindley French <[email protected]> wrote: > It sounds like that could be a pretty thin wrapper around std::thread. > > > On Tue, Mar 11, 2014 at 1:37 PM, Pieter Hintjens <[email protected]> wrote: >> >> The main joy of zthread is the zthread_fork method, which returns an >> "attached" thread with a pipe back to the caller. That is the basis >> for all the async classes like zbeacon and zauth. >> >> On Tue, Mar 11, 2014 at 9:10 PM, Turkey Breast <[email protected]> >> wrote: >> > oh thanks for pointing those classes out to me. I will port those too >> > eventually. >> > >> > no need for zthread though: >> > http://en.cppreference.com/w/cpp/thread/thread >> > and it's very well designed (you are required to either call join() or >> > detach()) >> > >> > >> > >> > >> > >> > On Tuesday, March 11, 2014 7:44 PM, Pieter Hintjens <[email protected]> >> > wrote: >> > If I was even moderately competent in C++ what I'd have done ages ago >> > is port the core CZMQ classes to C++, particularly zthread, and then >> > zbeacon, zauth, zcert, zcertstore. It is not a huge effort, given that >> > CZMQ already offers a class based API. >> > >> > As a temporary workaround, wrapping CZMQ is a fair compromise. It's >> > definitely the fastest way to get the security into your apps. >> > >> > >> > On Tue, Mar 11, 2014 at 6:29 PM, Lindley French <[email protected]> >> > wrote: >> >> While cppzmq isn't much of a wrapper, zmqpp is a bit better. I'm not >> >> thrilled with the idea of an entirely separate c++ binding just to get >> >> the >> >> czmq stuff. Any chance of integrating with zmqpp instead? >> >> >> >> >> >> On Tue, Mar 11, 2014 at 10:21 AM, Turkey Breast >> >> <[email protected]> >> >> wrote: >> >>> >> >>> Yes, I can make the neccessary changes but the API is still incomplete >> >>> and >> >>> evolving. Hope that's OK. But already it allows people to make use of >> >>> the >> >>> crypto stuff, and I'm migrating my project towards this wrapper. I >> >>> don't >> >>> think the previous cppzmq was well designed nor written. >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> On Tuesday, March 11, 2014 4:39 PM, Pieter Hintjens <[email protected]> >> >>> wrote: >> >>> Very nice! >> >>> >> >>> Can I interest you in http://zeromq.org/docs:organization? >> >>> >> >>> On Tue, Mar 11, 2014 at 3:27 PM, Turkey Breast >> >>> <[email protected]> >> >>> wrote: >> >>> > I've created this project for our project to wrap czmq in C++. The >> >>> > current ZMQ wrappers don't use CZMQ and don't implement the ZAP >> >>> > crypto >> >>> > handlers. >> >>> > >> >>> > https://github.com/darkwallet/czmqpp >> >>> > >> >>> > See examples/. It doesn't have everything but the core basics are >> >>> > there. >> >>> > >> >>> > Wherever possible I try to be consistent and not innovate on top of >> >>> > the >> >>> > CZMQ API. Return values are still ints and you can use the CZMQ API >> >>> > with >> >>> > CZMQ++ by calling self() on the objects to return the underlying >> >>> > pointer. >> >>> > >> >>> > _______________________________________________ >> >>> > zeromq-dev mailing list >> >>> > [email protected] >> >>> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> >>> >> >>> _______________________________________________ >> >>> zeromq-dev mailing list >> >>> [email protected] >> >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >>> >> >>> _______________________________________________ >> >>> zeromq-dev mailing list >> >>> [email protected] >> >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> >> >> >> >> >> >> _______________________________________________ >> >> zeromq-dev mailing list >> >> [email protected] >> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
