This topic describes the release notes for the TCP client SDK for C++. The release notes include the release date, download link, and feature updates for each release. You can select a version of the TCP client SDK for C++ that meets your business requirements to send and receive messages based on the description of this topic.
After you obtain the TCP client SDK for C++, you must prepare an environment based on the usage notes of the SDK for C++. The procedure for preparing an environment varies based on the version of the SDK.
For information about how to prepare an environment for the SDK V1.x.x , see Environment preparation (V1.x.x).
You can use the TCP client SDK for C++ V3.x.x to access only instances that contain namespaces. If the instance that you use does not contain a namespace, do not upgrade the TCP client SDK for C++ to V3.x.x.
By default, all ApsaraMQ for RocketMQ 5.x instances contain namespaces. If you use an ApsaraMQ for RocketMQ 4.x instance, you can check whether the instance contains a namespace in the Basic Information section of the Instance Details page in the ApsaraMQ for RocketMQ console.
3.x.x
Release date | Description | Download link |
2021-10-18 | Optimized feature Load balancing: Load balancing is performed based on messages. This makes message loads more balanced. Dashboard: Various metrics are added. The added metrics include the number of accumulated messages and the duration and success rate of each step from message production to message consumption. Message trace: More parameters are included in trace query results. These parameters are related to scheduled messages, delayed messages, transactional messages, and message consumption. Ordered messages: The maximum number of retries is changed to 16. Broadcasting consumption: The consumer offset can be customized when you start a consumer. Push mode: The consumption throttling feature is supported. The processing logic is optimized for scenarios in which the number of consumption threads is abnormal. Changes in API operations.
| ons-client-cpp |
Earlier versions
1.1.0
| Release date | Description | Download link for Windows | Download link for Linux |
| 2017-07-25 | Fixed issues - The following issue is fixed: Core dumps are caused when a consumer is shut down.
- The following issue is fixed: Access over HTTP is unavailable to the underlying URL class in Windows.
- The following issue is fixed: Timestamp errors occur in message traces.
- The following issue is fixed: Incorrect local IP addresses are displayed in message traces.
- Memory leaks in Windows are fixed.
| aliyun-mq-windows-cpp-sdk.zip | aliyun-mq-linux-cpp-sdk.tar.gz |
1.0.9
| Release date | Description | Download link for Windows | Download link for Linux |
| 2016-12-29 | Added features - Messages can be sent in one-way mode.
- Ordered messages are supported.
- The timeout period for sending messages can be set.
- The maximum number of retries for messages can be set.
Fixed issues - Resource leaks during shutdown are fixed.
- Core dumps during shutdown are fixed.
| None. | None. |
1.0.8
| Release date | Description | Download link for Windows | Download link for Linux |
| 2016-12-02 | Added features - The earlier version of the SDK for C# is no longer supported. An updated version of the SDK for C# is generated by using SWIG. The updated version provides more stable support for ASP.NET.
- Log paths can be customized.
- Built-in UTF-8 encoding is provided to support implicit encoding and decoding.
- The MQ_GUIDE documentation is provided. The ASP.NET demo is provided.
Optimized features - The boost library is updated to V1.6.2.
Fixed issues - The following issue is fixed: Core dumps occur when the producers or consumers of ordered messages are shut down.
| None. | None. |
1.0.7
| Release date | Description | Download link for Windows | Download link for Linux |
| 2016-11-15 | Added features - Consumption throttling is supported for consumers. By default, 1,000 messages are pulled and stored in the memory and then called back by the callback function one by one.
- Ordered messages are supported.
- The timeout period for sending messages can be set.
- The maximum number of retries for messages can be set.
Optimized features - The message tracing feature is optimized. A separate thread pool is used to send trace data.
- The granularity of the TCP lock is optimized.
Fixed issues - Issues related to message tracing are fixed.
- Core dumps caused by shutdown are fixed.
- Memory leaks are fixed.
- The following issue is fixed: An exception is thrown if a message tag contains double vertical bars (||).
| None. | None. |