RedisClient
providing both
synchronous
and
asynchronous
connections.See: Description
Package | Description |
---|---|
com.lambdaworks.codec | |
com.lambdaworks.redis | |
com.lambdaworks.redis.codec | |
com.lambdaworks.redis.output | |
com.lambdaworks.redis.protocol | |
com.lambdaworks.redis.pubsub |
RedisClient
providing both
synchronous
and
asynchronous
connections.
Multiple threads may share one connection provided they avoid blocking and transactional
operations such as BLPOP and
MULTI/EXEC.
Multiple open connections are efficiently managed by the excellent
netty NIO framework.
Each redis command is implemented by one or more methods with names identical to the lowercase
redis command name. Complex commands with multiple modifiers that change the result type include
the CamelCased modifier as part of the command name, e.g.
zrangebyscore
and
zrangebyscoreWithScores
.
Redis connections are designed to be long-lived, and if the connection is lost will reconnect
until close()
is called. Pending commands that have not timed out will be (re)sent after
successful reconnection.
All connections inherit a default timeout from their RedisClient
and will throw a RedisException
when non-blocking commands fail
to return a result before the timeout expires. The timeout defaults to 60 seconds and
may be changed via RedisClient.setDefaultTimeout(long, java.util.concurrent.TimeUnit)
or for
each individual connection.
Copyright © 2015. All rights reserved.