SubscriptionMode

RTM always tracks the position value for the subscription and tries to use it when resubscribing after the connection drops and the client reconnects.

If the position points to an expired message, the resubscription attempt fails. RTM sends an expired_position error and stops the subscription process.

If the subscription is active, and RTM detects that the current position value points to an expired message, the subscription is in an 'out-of-sync' state. In this case, RTM sends an out_of_sync error and unsubscribes you.

To learn more about position tracking and fast-forwarding, see the sections "... with position" and "... with fast-forward (advanced)" in the chapter "Subscribing" in Satori Docs.

RTM tracks the position value for the subscription and tries to use it when resubscribing after the connection drops and the client reconnects. If the position points to an expired message, RTM fast-forwards to the earliest position that points to a non-expired message.

This mode reliably goes to the next available message when RTM is resubscribing. However, RTM always fast-forwards the subscription if necessary, so it never returns an error for an 'out-of-sync' condition.

To learn more about position tracking and fast-forwarding, see the sections "... with position" and "... with fast-forward (advanced)" in the chapter "Subscribing" in Satori Docs.

RTM doesn't track the position value for the subscription. Instead, when RTM resubscribes following a reconnection, it fast-forwards to the earliest position that points to a non-expired message.

Because RTM always fast-forwards the subscription, it never returns an error for an 'out-of-sync' condition.

To learn more about position tracking and fast-forwarding, see the sections "... with position" and "... with fast-forward (advanced)" in the chapter "Subscribing" in Satori Docs.