Page History

...

...

• QPID-529: The C++ broker now supports priority-ordered message queuing.
• QPID-1916: The Java release now includes Maven artifacts for the Java client.
• QPID-2104: The C++ broker has an improved last-value queue implementation.
• QPID-2777, QPID-3009: There are new, experimental Perl, Python, and Ruby bindings for the C++ messaging API.
• QPID-2921: In the C++ broker, message completion is now an asynchronous operation in more situations.
• QPID-2934: C++ QMF agents can now authorize incoming method calls using an authentication ID passed with the corresponding message.
• QPID-2935: The C++ broker and client now implement flow control by default. Related: QPID-3081.
• QPID-2958: The .NET binding to the C++ client now targets an older version of the .NET Framework, 2.0, for broader compatibility.
• QPID-2966: The C++ broker now allows administrators to alter logging levels at runtime.
• QPID-3000: The C++ broker now optionally waits a configured time before removing auto-delete queues.
• QPID-3002: The C++ broker now generates alerts when queues reach a certain depth.
• QPID-3015: The C++ broker now supports creating queues and exchanges via QMF.
• QPID-3031: The C++ client now allows setting the SSL certificate name in the connection options.
• QPID-3032: You can now use more fine-grained ACLs to control QMF operations on the C++ broker.
• QPID-3067: Examples using the old messaging API have been isolated under a common directory.
• QPID-3115: Some cases where the C++ and python clients' connection options differed have been reconciled.

...