[zeromq-dev] C++ assertion failed with Java client

[Chuck Remes]

On Feb 3, 2012, at 3:47 AM, john skaller wrote:

> 
> On 03/02/2012, at 4:34 PM, Chuck Remes wrote:
> 
>> On Feb 2, 2012, at 11:21 PM, john skaller wrote:
>> 
>>> 
>>> On 03/02/2012, at 2:32 PM, Chuck Remes wrote:
>>> 
>>>> I can't imagine how it would be done cleanly. I haven't thought about it as deeply as you, but in my experience this will be very difficult if not impossible to achieve. I welcome being proven wrong. :)
>>> 
>>> Can you explain why simply setting a mutex at the start of every C API call,
>>> and releasing it at the end, would not work? the mutex object would
>>> live in the socket. 
>> 
>> I don't understand all the constraints of your Felix language, so anything I guess at would likely be wrong. 
> 
> Er, I'm confused. This has nothing to do with Felix.
> 
> I'm talking about the Zero MQ C API.

Then I'm confused too. I thought this discussion was in the context of Felix which, as you have noted a few times, uses thousands or millions of pthreads & fibers/coroutines behind the scenes. 

A mutex works fine with a 0mq socket so adding one to the socket itself would also work. I just don't think it would perform well plus everyone would have to pay that price even if they didn't need it. Yuck.

cr