1 <?xml version="1.0" ?>

     2 <api id="c5abe1a8714f500e6889205330ded96f" dataversion="1.0">

     3   <name>XIMP Core Protocol Plug-in API</name>

     4   <description>XIMP Framework Protocol Plugin API contains abstract interfaces what protocol adaptation plug-ins must implement. XIMP Framework will instantiate protocol plug-ins through ECom framework and call methods declared in these interfces. This interface includes methods to:

     5 - get the features of the protocol plug-in

     6 - manage the service connections</description>

     7   <type>c++</type>

     8   <subsystem>ximpfw</subsystem>

     9   <libs><lib name="ximpdatamodel.lib"/>

    10 <lib name="ximpoperations.lib"/>

    11 <lib name="ximpecomhook.lib"/>

    12 <lib name="ximpmanager.lib"/>

    13 <lib name="ximpsrvclient.lib"/>

    14 <lib name="ximpprocessor.lib"/>

    15 <lib name="ximputils.lib"/>

    16 </libs>

    17   <release category="domain"/>

    18   <attributes>

    19      <!-- This indicates wether the api provedes separate html documentation -->

    20      <!-- or is the additional documentation generated from headers. -->

    21      <!-- If you are unsuere then the value is "no" -->

    22      <htmldocprovided>yes</htmldocprovided>

    23      <adaptation>no</adaptation>

    24   </attributes>

    25 </api>