From 41ef526e8c13995dc6ef52f9c24a7611f636a108 Mon Sep 17 00:00:00 2001 From: John Blum Date: Thu, 8 Jun 2017 17:04:27 -0700 Subject: [PATCH] Fixup the README. --- README.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.adoc b/README.adoc index ee74d71..70a7122 100644 --- a/README.adoc +++ b/README.adoc @@ -3,18 +3,18 @@ image:https://badges.gitter.im/spring-projects/spring-session.svg[link="https:// image:https://travis-ci.org/spring-projects/spring-session.svg?branch=master["Build Status", link="https://travis-ci.org/spring-projects/spring-session"] = Spring Session Data Geode -John Blum _Spring Session_ aims to provide a common infrastructure for managing Sessions. -_Spring Session Data Geode_ aims to postion Pivotal GemFire or Apache Geode as a session repository provider. +_Spring Session Data Geode_ positions either https://pivotal.io/pivotal-gemfire[Pivotal GemFire] +or http://geode.apache.org/[Apache Geode] as a Session Repository provider. This provides many benefits including: -* Accessing a session from any environment (i.e. web, messaging infrastructure, etc) +* Accessing a Session from any environment (i.e. web, messaging infrastructure, etc) * In a web environment -** Support for clustering in a vendor neutral way -** Pluggable strategy for determining the session id +** Support for clustering in a vendor/technology neutral way +** Pluggable strategy for determining the Session ID ** Easily keep the HttpSession alive when a WebSocket is active == Code of Conduct