.. _section-index2416:

*******************************
Upgrading from 2.4.15 to 2.4.16
*******************************

See :ref:`section-Install-Upgrade`, if you haven't already.

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

.. attention::

  For important information on new and removed platforms and features in |me|
  2.4.16, see `Supported Platforms and Programming Languages
  <https://community.rti.com/static/documentation/connext-cert/2.4.16/doc/html/release/supported_platforms.html>`__
  and `What's New in 2.4.16
  <https://community.rti.com/static/documentation/connext-cert/2.4.16/doc/html/release/whats_new_2416.html>`__
  in the |me| documentation.

API Removal
-----------

|me| 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.

Zero Copy Transfer Compatibility
--------------------------------

|me| 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 |me| 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 |me| 2.4.15 applications that communicate with Zero Copy
transfer, make sure that you rebuild them with the 2.4.16 |me|
libraries. No further changes to your applications are required.