Spring HTTP Session implementation backed by ScaleOut StateServer

Introduction

The ScaleOut Spring HTTP Session library for Java allows developers to use ScaleOut StateServer to serve Java HttpSessions from the in-memory data grid to a Spring application. The library implements the spring-session-core Session and SessionRepository interfaces to store HTTP session objects within a specified Namespace in the in-memory data grid.

Our docs will get you up and running in no time.

To use the library in your project:

Gradle

For Gradle, you can add the ScaleOut API Repository to your build.gradle by adding the following under repositories:

repositories {
    mavenCentral()
    maven {
        url "https://repo.scaleoutsoftware.com/repository/external"
    }
}

...and then you can add the ScaleOut Spring Session API as a dependency:

compile group: 'com.scaleoutsoftware.spring', name: "session", version: '2.1'

Maven

For Maven, you can add the ScaleOut API Repository to your pom.xml by adding the following repository reference:

<repository>
    <id>ScaleOut API Repository</id>
    <url>https://repo.scaleoutsoftware.com/repository/external</url>
</repository>

...and then you can add the ScaleOut Spring Session API as a dependency:

<dependencies>
	<dependency>
	  <groupId>com.scaleoutsoftware.spring</groupId>
	  <artifactId>session</artifactId>
	  <version>2.1</version>
	</dependency>
</dependencies>

Usage

ScaleOut can be used a SessionRepository by using the EnableScaleoutHttpSession attribute.

The attribute has six parameters:

cacheName

The cacheName parameter defines the ScaleOut namespace the ScaleoutSessionRepository will use for storing session objects.

Default Value: SpringSessionRepo

maxInactiveTimeMinutes

The maxInactiveTimeMinutes parameter defines the maximum allowed time that a session can exist before expiring. The timeout used is sliding, such that after every access (findById(id) or save(session)) the timeout is reset.

Default value: 30

useLocking

The useLocking parameter tells the ScaleoutSessionRepository whether to lock Session's during access operations.

Note, locking required if GeoServer pull enabled.

Default value: true

remoteStoreName

The remoteStoreName parameter tells the ScaleoutSessionRepository to create objects with the GeoServer notify coherency policy and push creates and updates to a remote store specified by the parameter name. When two ScaleOut StateServer stores are configured for bi-directional pull replication using ScaleOut GeoServer Pro, this enables object updates to be replicated between both stores while allowing synchronized access to the objects.

Note, the useLocking parameter must be set to true.

Note, ScaleOut GeoServer® Pro is licensed separately from ScaleOut StateServer.

Default value: null (unused)

This library is open source and has dependencies on other ScaleOut Software products.

License: Apache 2