From ef63395b077570e8d86e4c45cdc1c60a218dc723 Mon Sep 17 00:00:00 2001 From: WalkerWatch Date: Tue, 7 Jun 2016 16:40:24 -0400 Subject: [PATCH] Removed references to SPDY in Chapter 3, updated Chapter 10 with general info on Sessions Signed-off-by: WalkerWatch --- .../sessions/setting-session-characteristics.adoc | 6 ++++++ .../quick-start/configuring/what-to-configure.adoc | 8 ++++---- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/jetty-documentation/src/main/asciidoc/administration/sessions/setting-session-characteristics.adoc b/jetty-documentation/src/main/asciidoc/administration/sessions/setting-session-characteristics.adoc index 9317a27a8fe..eaaf3c7bd2a 100644 --- a/jetty-documentation/src/main/asciidoc/administration/sessions/setting-session-characteristics.adoc +++ b/jetty-documentation/src/main/asciidoc/administration/sessions/setting-session-characteristics.adoc @@ -17,6 +17,12 @@ [[setting-session-characteristics]] === Setting Session Characteristics +Sessions are a concept within the Servlet api which allow requests to store and retrieve information across the time a user spends in an application. +Choosing the correct session manager implementation is an important consideration for every application as each can fit and perform optimally in different situations. +If you need a simple in-memory session manager that can persist to disk then the `HashSessionManager` can be a good place to start. +If you need a session manager that can work in a clustered scenario with multiple instances of Jetty, then the JDBC session manager can be an excellent option. +Jetty also offers more niche session managers that leverage backends such as MongoDB, Inifinispan, or even Google's Cloud Data Store. + To modify the session characteristics of a web application, you can use the following parameters, applying them as in one of the example configurations: [[using-init-parameters]] diff --git a/jetty-documentation/src/main/asciidoc/quick-start/configuring/what-to-configure.adoc b/jetty-documentation/src/main/asciidoc/quick-start/configuring/what-to-configure.adoc index 87e430bcfcb..2c12a63c57d 100644 --- a/jetty-documentation/src/main/asciidoc/quick-start/configuring/what-to-configure.adoc +++ b/jetty-documentation/src/main/asciidoc/quick-start/configuring/what-to-configure.adoc @@ -55,7 +55,7 @@ Services:: ==== Configuring Connectors A Jetty Server Connector is a network end point that accepts connections for one or more protocols which produce requests and/or messages for the Jetty server. -In the standard Jetty server distribution, several provided configuration files add connectors to the server for various protocols and combinations of protocols: `http.ini`, `https.ini` and `jetty-spdy.xml`. +In the standard Jetty server distribution, several provided configuration files add connectors to the server for various protocols and combinations of protocols: `http.ini`, `https.ini` and `jetty-http2.xml`. The configuration needed for connectors is typically: Port:: @@ -67,10 +67,10 @@ Host:: Idle Timeout:: The time in milliseconds that a connection can be idle before the connector takes action to close the connection. HTTP Configuration:: - Connector types that accept HTTP semantics (including HTTP, HTTPS and SPDY) are configured with a HttpConfiguration instance that contains common HTTP configuration that is independent of the specific wire protocol used. - Because these values are often common to multiple connector types, the standard Jetty Server distribution creates a single HttpConfiguration in the `jetty.xml` file which is used via the XML Ref element in the specific connector files. + Connector types that accept HTTP semantics (including HTTP, HTTPS and HTTP2) are configured with a `HttpConfiguration` instance that contains common HTTP configuration that is independent of the specific wire protocol used. + Because these values are often common to multiple connector types, the standard Jetty Server distribution creates a single `HttpConfiguration` in the `jetty.xml` file which is used via the XML Ref element in the specific connector files. SSL Context Factory:: - The TLS connector types (HTTPS and SPDY) configure an SSL Context Factory with the location of the server keystore and truststore for obtaining server certificates. + The TLS connector types (HTTPS and HTTP2) configure an SSL Context Factory with the location of the server keystore and truststore for obtaining server certificates. ____