[zeromq-dev] How fast inproc socket REQ/DEALER create/destroy lifecycle?
Pieter Hintjens
ph at imatix.com
Fri Sep 20 20:26:20 CEST 2013
True, it is often quite subtle how the simple solutions emerge, and
sometimes they just don't.
What can help is to build higher level APIs - I've done this a lot in
CZMQ and FileMQ and similar projects to create abstractions that work
as I'd like, hiding the complexity.
On Fri, Sep 20, 2013 at 7:42 PM, Artem Vysochyn
<artem.vysochyn at gmail.com> wrote:
> No problem et al. In general, I really love ZMQ, it teaches me always
> think towards finding most simple-and-effective solutions. But it's always
> "it depends" on what ppl mean under "clumsy way".
>
> And when I originally wrote a code which has been sending correlation_id
> along inside message, after couple of weeks I reverted this, because this
> seemed to me so weird and ugly, and I had been inlighted like "hey! just
> create and destroy inproc sockets! they are cheap, they aren't tcp ones, so
> u are safe." But then I stucked with FD limit issue even for inproc, and
> got completely stucked.
>
>
> Well, now, after your clarification, I see how it should be.
>
>
>
>
> 2013/9/20 Pieter Hintjens <ph at imatix.com>
>>
>> Sorry if I sound like I'm just telling you to RTFM, but this is a
>> common symptom when starting to learn 0MQ, trying to solve problems in
>> a clumsy way when there's a simpler way that you see when you've
>> internalized the way things work. There seems to be no alternative
>> except to work through it.
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
More information about the zeromq-dev
mailing list