generic-library/libzmq
1
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2024-12-13 10:52:56 +01:00
Code Issues Projects Releases Wiki Activity

Update NEWS for 2.0.7 release

Browse Source
This commit is contained in:
Martin Lucina 2010-06-04 19:20:37 +02:00
parent 9b8f902d72
commit e8a9614aae
1 changed files with 39 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
NEWS
View File

@ -1,30 +1,54 @@
0MQ version 2.0.7 (Beta), released on 2010/06/XX 0MQ version 2.0.7 (Beta), released on 2010/06/04
================================================ ================================================
Distribution
------------
* The core documentation has been updated with many clarifications, especially
in the description of the functionality provided by the different socket
types.
* The version of OpenPGM bundled with 0MQ has been updated to the 2.1.26 release.
Interface Interface
--------- ---------
* zmq_init has a single parameter now: number of I/O threads in the thread pool. * The zmq_init() function now has only a single parameter; the number of 0MQ
All the remaining parameters where dropped. I/O threads to create in the context being initialised. The app_threads and
* ZMQ_P2P socket type was renamed to ZMQ_PAIR. flags parameters have been removed.
* LWM socket option was dropped.
* The ZMQ_P2P socket type has been renamed to ZMQ_PAIR.
* The ZMQ_LWM socket option has been removed; the low water mark for a socket
is now computed automatically by 0MQ.
New functionality New functionality
----------------- -----------------
* Multi-hop REQ/REP pattern is fully supported. This feature allows to put * Multi-hop request/reply is fully supported. This feature allows the insertion
a device(s) between REP and REP sockets thus allowing for scenarios like of device(s) between ZMQ_REQ and ZMQ_REP sockets thus enabling scenarios
multi-threaded server, shared service queue etc. The whole infrastructure such as multi-threaded server, shared service queue, and other interesting
is transparent to the applications. messaging topologies. The entire infrastructure is transparent to
applications.
* Multi-part messages. Message may now be composed from several parts. This * Multi-part messages. A 0MQ message may now be composed of 1 or more message
feature allows for seamless zero-copy message passing when data are scattered parts; each message part is an independent zmq_msg_t in its own right. 0MQ
in the memory. Moreover it gives 0MQ message some basic structure. ensures atomic delivery of messages; peers shall receive either all message
parts of a message or none at all.
This feature allows for seamless zero-copy message passing when data are
scattered in memory, and is an important building block for multi-hop
messaging topologies.
* Context termination and ETERM. The zmq_term() function has been
changed to interrupt any blocking operations on open sockets, causing them to
return the newly defined ETERM error code. This allows for orderly
application termination, especially when multiple application threads are
involved.
* Sane termination of multiple threads. This means that main thread can
terminate the messaging library causing all blocking functions to unblock
and allow for orderly application termination.
0MQ version 2.0.6 (Beta), released on 2010/03/16 0MQ version 2.0.6 (Beta), released on 2010/03/16
================================================ ================================================