-
Notifications
You must be signed in to change notification settings - Fork 4
Stateful connections
spinach's API is separated into a DisqueConnection
API and multiple command APIs (sync, async and reactive) to separate connection resources from the particular API. Every API operates on the stateful connection that maintains the state (authentication state for now). This state is restored after the connection reconnects. All async, sync and reactive API's operate on the underlying connection. If you close for example the connection using the sync API, the same connection is no longer usable over the async or reactive API. Multiple connections (multiple calls to connect()
) create multiple connections that are isolated from each other.
You can obtain a stateful connection from an existing connection by calling getConnection()
on the async, sync, or reactive API.
This wiki and the README document contains a lot of information, please take your time and read these instructions carefully.
If you run into any trouble, you may start with getting started.
We provide detailed changes for each spinach release.
Be sure to read the CONTRIBUTING guidelines before reporting a new lettuce issue or open a pull request.
If you have any questions about the lettuce usage or want to share some information with the community, please go to one of the following places:
More resources:
- Javadoc
- Build status: Travis CI
- All versions: Maven Central
- Snapshots: Sonatype OSS Repository
Intro
Getting started
Advanced usage
- QueueListener API
- SocketAddress Supplier API
- Client options
- SSL Connections
- Unix Domain Sockets
- Connection Events
- Command Interfaces
- Stateful Connections
Integration and Extension
- Codecs
- CDI Support (future)
- Spring Support (future)
Internals