DDS4CCM_ — Do we need the Multi* interfaces/ports?

I have been thinking of how I could use the Multi* interfaces/ports. I can
imagine that a component developer first starts to use the basic ports and
when he is more concerned with efficiency/performance he wants to use the
Multi ports where he can send batches of data to DDS in one call. This looks
nice, but when he wants todo that, he has to use different ports, which
leads to a different component design. It is just not an easy change to make
a new implementation of the component, it will become something completely
different by use the other ports. No easy swap to a more efficient component
implementation.

I think we should remove all Multi ports and merge their functionality into
the regular ports. That way a component developer can use the more efficient
sequences based interfaces without large changes in models and deployment
plants.

Merge the multi-operations with the simple ones in a consolidated interface:
Writer + MultiWriter ¨ Writer
Updater + MultiUpdater ¨ Updater
RawListener + MultiListener ¨ Listener
StateLisener + MultiLisener ¨ StateListener
Take the opportunity of this recast of the IDL description for the DDS ports, to
better harmonize the names of the operations and to rationalize the roles of each
interface.