SAP ABAP Data Element SSI_WEBSOCKET_SESSION_MODE_DIS (WebSocket Session Handling)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CST (Application Component) Client/Server Technology
⤷
SSI_MSG (Package) Messaging

⤷

⤷

Basic Data
Data Element | SSI_WEBSOCKET_SESSION_MODE_DIS |
Short Description | WebSocket Session Handling |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 64 | |
Decimal Places | 0 | |
Output Length | 64 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Session |
Medium | 20 | Session Handling |
Long | 40 | Session Handling |
Heading | 55 | Session Handling |
Documentation
Definition
Type of WebSocket session handling
- Stateless: For each incoming WebSocket message a new session is created in which the message is processed. Afterwards this session will be deleted. Multiple sessions can exist in parallel.
- Stateful: A specific session is assigned to the WebSocket. All incoming WebSocket messages are processed in succession in this session.
- None: This session handling can only occur temporarily when the client connection is closing. In this case the assignment of the WebSocket to this session has already been removed.
Client connections are always stateful (unless the connection is just closing). For server connections both types of session handling (stateless and stateful) are possible. If a WebSocket is stateful, the session assigned to the WebSocket can be removed from the column "Session Key".
Use
Dependencies
Example
History
Last changed by/on | SAP | 20140117 |
SAP Release Created in | 740 |