Updated Features
This commit is contained in:
10
index.html
10
index.html
@@ -46,10 +46,14 @@ Spring Session provides an API and implementations for managing a user’s sessi
|
||||
|
||||
## Features
|
||||
|
||||
Spring Session also provides transparent integration with:
|
||||
Spring Session provides the following features:
|
||||
|
||||
* HttpSession - allows for simple clustered sessions, obtaining the session from custom parts of the HTTP request (i.e. HTTP headers), and managing multiple user’s sessions in a single browser instance (i.e. multiple authenticated accounts similar to Google).
|
||||
* WebSocket - provides the ability to keep the HttpSession alive when receiving WebSocket messages
|
||||
* API and implementations for managing a user's session
|
||||
* **HttpSession** - allows replacing the HttpSession in an application container (i.e. Tomcat) neutral way
|
||||
** **Clustered Sessions** - Spring Session makes it trivial to support clustered sessions without being tied to an application container specific solution.
|
||||
** **Multiple Browser Sessions** - Spring Session supports managing multiple users' sessions in a single browser instance (i.e. multiple authenticated accounts similar to Google).
|
||||
** **RESTful APIs** - Spring Session allows providing session ids in headers to work with RESTful APIs
|
||||
* **WebSocket** - provides the ability to keep the HttpSession alive when receiving WebSocket messages
|
||||
|
||||
|
||||
<span id="quick-start"></span>
|
||||
|
||||
Reference in New Issue
Block a user