How to implement RFA provider with hotstandby enabled ?

Hello,

We're implementing a RFA provider in OMM and the feature "hot standby" is enabled on our TREP infrastructure but we don't have any documentation about this feature.

Is it related to "warm standby" or is it totally different ?

In the RFA documentation, we can read about "warm standby":

"a provider can be told to run as an Active or a Standby server, where the Active will behave as usual. The Standby will respond to item requests only with the message header and will forward any state changing information."

Do we have to implement the same behavior for "hotstandby" ?

When starting our provider, we have a message like this telling that "hot standby" is enabled:

<!-- Incoming Message from 'mkddev306' on 'localhost' interface -->
<!-- Time: 18:23:39:356 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<genericMsg domainType="RSSL_DMT_SOURCE" streamId="2" containerType="RSSL_DT_MAP" flags="0x14 (RSSL_GNMF_HAS_MSG_KEY|RSSL_GNMF_MESSAGE_COMPLETE)" dataSize="37">
  <key  flags="0x2 (RSSL_MKF_HAS_NAME)"  name="ConsumerStatus"/>
  <dataBody>
    <map flags="0x0" countHint="0" keyPrimitiveType="RSSL_DT_UINT" containerType="RSSL_DT_ELEMENT_LIST" >
      <mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="1" >
        <elementList flags="0x8 (RSSL_ELF_HAS_STANDARD_DATA)">
          <elementEntry name="SourceMirroringMode" dataType="RSSL_DT_UINT" data="2"/>
        </elementList>
      </mapEntry>
     </map>
  </dataBody>
</genericMsg>

This message tells that our provider is on standby (cf. SourceMirroringMode = 2), so do we have to send only message with headers and no payload (like the "warm standby") ?

Thanks your answers.

Regards.