Welcome to Distributor Discussions!

[hoddmimes]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[hoddmimes]

PoBe developer. Reliable multicast/broadcasts is a special niche of true one-to-many distribution. True one-to-many broadcast service is using OSI Level 2 that does not guarantee support for sending but not receiving multicast IP datagrams. Nor is order of datagram guaranteed.

Mostly one-to-many broadcast service are related to video / audio distribution where loss of data is not essential. Loss of data may affect the quality of the service but the service may be acceptable anyway. For this purpose a number of standard protocols and implementation are available RTP, RTMP, RTSP, etc.

Reliable multicast/broadcast service require data;

• Data is not loss.
• Data is delivered in right sequence.
• Data is not duplicated i.e only delivered once.
• If the service can not maintained the service criteria above, consumers must be notified. At that point all recovery possibilities are considered to been exhausted.

The demand for reliable broadcast services is fairly limited. It has to my knowledge been mostly required by financial trading. services. With limited demand there has not been a an interest for industry standard protocols and implementations.
A few protocols exists, see Wikipedia

They may meet your criteria, but have never been we where looking for where the we where looking for:

• High real-time message rates
• Hide recover and synchronization mechanism for consumers/producers.
• Guaranteed delivery or exception notification