From af5899fb1a43a2c50da75e04aae0da4a83a083c3 Mon Sep 17 00:00:00 2001 From: Mark Anderson Date: Mon, 31 Aug 2015 21:17:30 +0100 Subject: [PATCH] Fix inconsistency in docs when describing delete/expired events for Redis. --- docs/src/docs/asciidoc/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/docs/asciidoc/index.adoc b/docs/src/docs/asciidoc/index.adoc index 45056b03..68f24daf 100644 --- a/docs/src/docs/asciidoc/index.adoc +++ b/docs/src/docs/asciidoc/index.adoc @@ -448,7 +448,7 @@ The `SessionRepository.getSession(String)` method ensures that no expired sessio This means there is no need to check the expiration before using a session. ==== -Spring Session relies on the expired and delete http://redis.io/topics/notifications[keyspace notifications] from Redis to fire a <> and <> respectively. +Spring Session relies on the delete and expired http://redis.io/topics/notifications[keyspace notifications] from Redis to fire a <> and <> respectively. It is the `SessionDeletedEvent` or `SessionExpiredEvent` that ensures resources associated with the Session are cleaned up. For example, when using Spring Session's WebSocket support the Redis expired or delete event is what triggers any WebSocket connections associated with the session to be closed.