First page Back Continue Last page Graphics

Conforming to PPR Guidelines


Conforming to PPR Guidelines

When PPR is implemented correctly, it improves application performance as follows:

Rendering performance is improved by generating only a subset of the page.

Network traffic is reduced by sending only a subset of the page’s contents to the browser.

User perception of performance is improved because of not spending time looking at a blank page.

When performance improvement is not possible with PPR, it should not be implemented, thus avoiding unnecessary code bloat.

PPR should not be invoked in the following contexts:

When navigating to another page, because some page elements, such as page titles, do not change during PPR

When response times may be long (user is blocked during a partial page submit), such as:

Database queries or database maintenance operations

Processes that demand significant middle-tier processing

When multiple sections of the page need to be redrawn, such as:

Action or choices that affect more than half the content of the page

Inline messaging, which features a message box at the top of the page, and may insert inline messages below multiple fields