[zeromq-dev] client/server sockets -- stability

Luca Boccassi luca.boccassi at gmail.com
Mon Oct 16 20:00:32 CEST 2017

On Mon, 2017-10-16 at 11:53 -0400, Bill Torpey wrote:
> Hi All:
> Without going into too much detail (I’ll save that for another post
> when I’ve gotten all my ducks in a row), it looks like I’ve found a
> solution to the problems I’ve been having using different socket
> types to do inter-thread synchronization, which ends up being
> client/server sockets over inproc.  (Which ironically has nothing to
> do with their thread-safety, but everything to do with the fact that
> sends will block until the message can be queued/delivered).
> I notice the disclaimer that these are drafts and subject to change,
> etc., so my question is whether there is any expectation around when
> these socket types will be declared “stable”?  
> Can anyone shed any light on the process needed to move these to
> stable status, and/or what the timeframe might be?
> Many thanks in advance for any help!
> Regards,
> Bill Torpey

Documentation is missing, and also there was still recently some
brainstorming on how to do something akin to multipart in the new
sockets, which might require API breakages:


Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20171016/b3eb4b28/attachment.sig>

More information about the zeromq-dev mailing list