Open topic with navigation

# Prefetch: Enabled Versus Disabled

As covered earlier, a standard durable represents the interest of one subscriber object and forwards messages to the subscriber on request. The type of persistence for a standard durable depends on whether prefetch is enabled or disabled.

The following diagram illustrates two networks, Network A and Network B. In both networks, each publisher represents potentially many program processes, all of which publish on the same endpoint. Each subscriber represents potentially many program processes. There is one durable per subscriber. The store maintains interest in the message stream even when subscriber is absent.

In Network A, prefetch is enabled and the persistence store functions as a message broker, with no messages traveling from the publisher endpoint to the subscriber endpoint.

In Network B, prefetch is disabled and messages typically flow via a direct path transport from the publisher endpoint to the subscriber endpoint. The direct path transport is backed by the store that receives the message stream from the publisher endpoint and retains each message until the subscriber acknowledges (replies to) the message. The store retains unacknowledged messages if the subscriber is absent or the direct path fails and then retransmits the messages to the subscriber, as needed.

Figure 12: Prefetch Enabled and Prefetch Disabled

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.