summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorMartin Sustrik <sustrik@250bpm.com>2010-06-04 18:49:55 +0200
committerMartin Sustrik <sustrik@250bpm.com>2010-06-04 18:49:55 +0200
commit9b8f902d72438752b00d4c1bb3887c40423777e0 (patch)
treeaf2ba26a73860e879cdba557e8c390dfbb3a2347 /NEWS
parentbaf659fde5136c20f879ef713ec3effc34854ba6 (diff)
initial version of 2.0.7 NEWS
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS25
1 files changed, 24 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 40584b5..491fc41 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,30 @@
0MQ version 2.0.7 (Beta), released on 2010/06/XX
================================================
-...
+Interface
+---------
+
+* zmq_init has a single parameter now: number of I/O threads in the thread pool.
+ All the remaining parameters where dropped.
+* ZMQ_P2P socket type was renamed to ZMQ_PAIR.
+* LWM socket option was dropped.
+
+
+New functionality
+-----------------
+
+* Multi-hop REQ/REP pattern is fully supported. This feature allows to put
+ a device(s) between REP and REP sockets thus allowing for scenarios like
+ multi-threaded server, shared service queue etc. The whole infrastructure
+ is transparent to the applications.
+
+* Multi-part messages. Message may now be composed from several parts. This
+ feature allows for seamless zero-copy message passing when data are scattered
+ in the memory. Moreover it gives 0MQ message some basic structure.
+
+* 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
================================================