[zeromq-dev] Asynchrony in malamute clients

[Pieter Hintjens]

Yes, an issue in the Malamute repo is best, with a link to a minimal
test case. Thanks!

On Sun, Apr 12, 2015 at 9:27 PM, Kenneth Adam Miller
<kennethadammiller at gmail.com> wrote:
> I mean a github issue on the malamute repo.
>
> On Sun, Apr 12, 2015 at 3:27 PM, Kenneth Adam Miller
> <kennethadammiller at gmail.com> wrote:
>>
>> It is reproduced in that git repo that I linked at the bottom of my last
>> email, and the main file for that is very short. I've been struggling with
>> subtly for several weeks. Ha, I'm so happy to have found it!
>>
>> Would you prefer that I create one in github?
>>
>> On Sun, Apr 12, 2015 at 3:17 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>>
>>> On Sun, Apr 12, 2015 at 7:59 PM, Kenneth Adam Miller
>>> <kennethadammiller at gmail.com> wrote:
>>>
>>> > Key here is the message client A sent is persisted, but if this were
>>> > swapped
>>> > out for service semantics APIs, the tool would hang at client B
>>> > reading.
>>>
>>> Hmm, I think the service queue should keep messages around until B
>>> connects. If you can reproduce this not happening, please make an
>>> issue and I'll look at it.
>>>
>>> -Pieter
>>> _______________________________________________
>>> 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
>