[zeromq-dev] Assertion failure in pull.cpp
sustrik at 250bpm.com
Sat Aug 21 18:59:34 CEST 2010
On 08/21/2010 11:35 AM, Jon Dyte wrote:
>> The main lesson here seems to be that 0MQ will have to do pattern
>> verification so that it catches errors like this.
> yes it was suggested earlier and martin has confirmed it's doable . the
> zmq_init_t is the place for it, as far I can see.
Yes. It's doable. You are right, zmq_init_t is the right place do it.
The only problem is that it breaks the wire-level interop.
> I'd have to check if the inproc stuff makes use of that though.
Inproc is different from other transports in quite a few respects. As
for the type checking, there's an inproc registry inside ctx_t. Now it's
just a map from endpoint name to socket pointer. It should be enhanced
to hold the socket type as well, so that the connecting party knows what
socket it is connecting to.
More information about the zeromq-dev