I've mined the features section from the JIRA release notes, but stuff not in JIRA may have been overlooked, so please review and comment.

--Rafael


The Apache Qpid community is pleased to announce the release of Apache
Qpid M4!

Apache Qpid is a cross platform enterprise messaging solution which
implements the Advanced Message Queueing Protocol (http://www.amqp.org).
It provides brokers written in Java and C++ and clients in C++, Java
(including a JMS implementation), .Net, Python, and Ruby.

New features included in this release are:

  [QPID-106]  -  SSL for C++ broker
  [QPID-107]  -  ACL and RBAC
  [QPID-528]  -  Support message ttl
  [QPID-957]  -  CLI for extract information from Apache Qpid Java broker
  [QPID-1174] -  Remote Management Agent for management of external components
  [QPID-1209] -  Port to Windows
  [QPID-1248] -  Add "last image caching" so a new subscriber immediately gets 
the most recently sent msg
  [QPID-1277] -  .net AMQP 0.10 support
  [QPID-1279] -  Application level status communication
  [QPID-1281] -  .Net WCF support (0.10)
  [QPID-1288] -  Python API for Management Console Access
  [QPID-1290] -  Add ability to move messages from one queue to another
  [QPID-1293] -  .net Excel Add In
  [QPID-1296] -  Add SSL support to java client
  [QPID-1297] -  Add ACL support for federation
  [QPID-1334] -  JMX Management Console for Qpid Java broker
  [QPID-1339] -  failover and replay for the 0-10 java client
  [QPID-1348] -  Dynamic binding for federation links
  [QPID-1349] -  Push routing for Federation
  [QPID-1366] -  C++ Broker Federation - Automatic configuration of anti-looping

It is available to download from:

  http://www.apache.org/dist/qpid/M4/

Complete release notes are available here:

  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&styleName=Html&version=12313279

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to