2. Upgrading from 2.4.15 to 2.4.16

See Important: How to Use this Guide, if you haven’t already.

The following sections describe how to upgrade from Connext Cert 2.4.15 to Connext Cert 2.4.16. They describe general, wire, and other compatibility issues between Connext Cert 2.4.16 and previous releases.

Attention

For important information on new and removed platforms and features in Connext Cert 2.4.16, see Supported Platforms and Programming Languages and What’s New in 2.4.16 in the Connext Cert documentation.

2.1. API Removal

Connext Cert 2.4.16 no longer supports the ability to specify a locator address (such as 127.0.0.1) without a transport name prefix. For example, if you register a transport with the name udp and for the address 127.0.0.1, you must specify the locator as udp://127.0.0.1. Using a locator address without a transport name prefix will cause the associated DomainParticipant or endpoint creation to fail and return NULL.

To migrate your application(s) to 2.4.16, make sure that you add an appropriate transport name prefix to all locator addresses.

2.2. Zero Copy Transfer Compatibility

Connext Cert 2.4.16 includes a fix for an issue that two applications would fail to communicate with the Zero Copy v2 transport when they were started from different working directories. As a result of this fix, applications using an older version of Connext Cert Zero Copy transfer (such as 2.4.15) will not be able to communicate with applications using Zero Copy transfer in 2.4.16 onward.

If you have multiple Connext Cert 2.4.15 applications that communicate with Zero Copy transfer, make sure that you rebuild them with the 2.4.16 Connext Cert libraries. No further changes to your applications are required.