Session Handling
BSP applications can be implemented as both stateful and stateless applications. The term stateless does not mean that request data for a running application is not retained on principle; it refers to whether in the SAP Web Application Server the application context (also called
Roll Area) is retained for individual requests, or whether it is released following each request.If you want to keep large datasets about request limits in the server (in internal tables), this can be done either by working in stateful mode, that is, retaining data using the
Application Class or by Using Server-Side Cookies in a stateless application.Both ways have advantages and disadvantages, which are explained in the following sections.
A running BSP application – regardless of whether it is HTTP stateful or stateless is referred to as a session from here on. The start and end of a session is determined either by the user externally (compare
System-Specific URL-Parameters) or by the application itself and then only the end is determined.The following topics are dealt with: