The RAPCache subscriber receives messages from publishers and loads them into the RAPCache database.
RAPCache subscriber queues messages that are consumed by a data stream handler, which routes the messages to their final destination.
Subscribers receive message packets from publishers on multiple data streams. When a packet arrives, the subscriber records that the packet arrived. This record is used to identify any missing packets. If a packet is missing, the subscriber requests a resend from the publisher for that specific packet.
For high-volume usage, sites can run a second RAPCache subscriber on another machine to process file transfers.