Paged Feeds

A paged feed is a feed that has been split into pages (also known as segments) to improve system performance in delivering large feed documents and to improve performance for consuming a feed. A paged feed is presented with first, last, next, and previous links to allow access to additional pages in the feed document.

Paged feeds are supported for scheduled feeds only. The framework supports paged feeds via Integration Broker message segments. %MaxMessageSize is recommended when creating Integration Broker message segments for paged feeds.

When setting the paging property for a feed, select either Segmented or No Paging to determine how the framework displays the complete feed:

• Segmented

  • This option is designed for feeds intended for crawlers or system synchronization.

  • This option is not supported by most feed readers or clients.

  • Feed links (first, next, previous, last) are added to the feed XML.

  • Feed entries are not restricted by the Max Rows Limit parameter.

    See Setting Feed Publishing Framework Options.

• No paging

  • This option is designed for feeds intended for end user viewing.

  • This option is supported by all feed readers or clients.

  • Feed entries are restricted by the Max Rows Limit parameter.

The following table describes how paged feed options and Integration Broker message segment options affect the output of the framework:

Integration Broker Message Option	Feed Option - Segmented	Feed Option - No Paging
Segmented	Each message segment becomes a page in the feed XML. Oldest message contents appear first. The Max Rows Limit is not applicable.	All message or message segments appear in a single feed XML. Latest message contents appear first. The Max Rows Limit applies.
Non-segmented	Each message becomes a page in the feed XML. Oldest message contents appear first. The Max Rows Limit is not applicable.	All message content entries appear in a single feed XML. Latest message contents appear first. The Max Rows Limit applies.