Interoperability
================

.. Release Notes from this point.

:major:`[Major]` Zero Copy communication failed when applications were started from different directories
---------------------------------------------------------------------------------------------------------
When two applications were started from different working directories,
they would fail to communicate when using the Zero Copy v2 transport.

.. note::
    
  As a result of this fix, the Zero Copy transfer feature is not backwards
  compatible. Applications using an older version of |me| Zero Copy transfer
  will not be able to communicate with applications using Zero Copy transfer
  from 2.4.16 onward.


[RTI Issue ID MICRO-10391]

:minor:`[Minor]` OSAPI_SharedMemorySegment_get_max_size() functioned incorrectly on QNX systems
-----------------------------------------------------------------------------------------------
In the previous release, Linux and QNX systems shared the same
implementation of the ``OSAPI_SharedMemorySegment_get_max_size()``
function. This function only supported the ``/proc/sys/kernel/shmmax``
path on Linux systems; calling ``fopen()`` on this path on a QNX system
would fail and return the default shared memory maximum size.

This release continues to use ``/proc/sys/kernel/shmmax`` for Linux
systems, but now returns the default shared memory maximum size directly
for QNX systems without requiring a failed call to ``fopen()``.

.. note::

  This fix was made to the reference Platform Support Library (PSL)
  implementation, which is included in the PSL source as an example. The
  reference PSL is *NOT* part of certified product code.


[RTI Issue ID MICRO-8879]