Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This pertains to uPortal 3.3 and later

Rendering Pipeline Overview

The rendering pipeline uses a combination of XML Streaming APIs (StAX) and a custom Character Streaming API which mimics the StAX APIs but handles character and portal specific data. The rendering pipeline is comprised of small components each with a specific function. These components use a common input and output API allowing the runtime pipeline to be easily modified. Also all components are cache aware and can return a CacheKey that represents their current state for a request. This allows caching components to short-circuit the rendering pipeline when the output from a lower-level component is already in cache.

Key Components

While the rendering pipeline has

Detailed Pipeline Diagram

The diagram below represents the actual default uPortal rendering pipeline configuration.

  • No labels