[zeromq-dev] Important: backward incompatible changes for 0MQ/3.0!

gonzalo diethelm gdiethelm at dcv.cl
Wed Mar 23 22:41:01 CET 2011


> Hmm, currently inproc:// is weird, e.g. it doesn't allow connect
> before bind. So a weird name fits.

That's something else that should be fixed in 3.0 or even 2.1, so that inproc works like the rest of the protocols.

I add two more things (which I wrote as a comment on the web page):

The memory allocator should be extensible (think of an allocator strategy); same thing for the disk swap. What I mean by "strategy" is that it should be possible to plug one's own implementation of these things (memory allocator, disk swapper). Both should have default internal implementations.

-- 
Gonzalo Diethelm




More information about the zeromq-dev mailing list