Upgrading to 4.1 from 4.0
These are the breaking changes in 4.1:
- zmq_event_t has gone; in 4.0 the socket monitor sent this C/C++ structure across the connection. This did not however work well for other languages. In 4.1, the socket monitor sends a binary formatted message that is consistent across all languages.
- ZMQ_STREAM sockets now return an empty message upon client connect and/or disconnect. This no longer happens unless you set the ZMQ_STREAM_NOTIFY option on the socket.
- Previously an outgoing connection had a pipe before authentication. In 4.1, the pipe is created after successful authentication. This means sending to a socket without any successfully authenticated socket will now block unless there's a timeout or poll.
- The sizeof(zmq_msg_t) changed from 32 bytes to 64 bytes.
- zmq_msg_gets(&msg, "Peer-Address") returns the IPv4(/IPv6) address (for STREAM sockets)
Written: 23 Jun 2014 17:51
Revised: 03 Mar 2015 11:25
If you found this page useful, please rate it up so others will find it.
Edit this page | Tags | Print
See also
- An Introduction to ØMQ
- Builds
- Contributing
- Guidelines for ØMQ bindings
- Installing on Windows
- libzmq Source Git Repository
- Mailing Lists
- Message API Goals
- ØMQ Cookbook
- ØMQ Distributions
- ØMQ Labs
- ØMQ Owners
- ØMQ Release Policies
- ØMQ/2.1 Class Diagram
- ØMQ/3.0 Roadmap
- ØMQ/3.2 Roadmap
- Organization
- Process Manager
- Projects using ØMQ
- Release notes for ØMQ/4.0.0
- Reporting and Tracking an Issue
- Style
- The native ØMQ API (libzmq)
- The ØMQ Guide
- The Ten Minute Talk
- Trademark Policy
- Tuning ØMQ
- Upgrading from 2.0 to 2.1
- Upgrading from libzmq 2.x to 3.2
- Using Valgrind
- Welcome from AMQP
- ZDevices
- ZeroMQ Feature List
Who's watching this page?
... and more
page revision: 11, last edited: 03 Mar 2015 11:25