Storing the Application State
Portal components and services are stateless. However, a portal application needs to maintain its state; for example, the status of data handling.
The Portal Runtime enables you to store and share data for a portal component or service at different levels, depending on the required scope:
|
Scope |
Description |
|---|---|
|
Session |
A user session. Use to share data during an entire user session. |
|
Component |
A portal component. Use to store data specific to a component or an iView based on this component. The data is valid only during the component session. |
|
Request |
A single HTTP request and response cycle. Use to share data between all components running in the same request cycle. |
We recommend not to store large amounts of data at any level, because this may impact performance. For example, session failover mechanisms rely on copying session data across different cluster nodes. If the session is overloaded with data, this may cause a performance overhead.
For more information about state management in portal applications, see Managing State .