<?xml version="1.0"?>
<doc>
<assembly>
<name>ServiceStack.Redis</name>
</assembly>
<members>
<member name="T:ServiceStack.Redis.BasicRedisClientManager">
<summary>
Provides thread-safe retrievel of redis clients since each client is a new one.
Allows the configuration of different ReadWrite and ReadOnly hosts
</summary>
<summary>
BasicRedisClientManager for ICacheClient
For more interoperabilty I'm also implementing the ICacheClient on
this cache client manager which has the affect of calling
GetCacheClient() for all write operations and GetReadOnlyCacheClient()
for the read ones.
This works well for master-slave replication scenarios where you have
1 master that replicates to multiple read slaves.
</summary>
</member>
<member name="M:ServiceStack.Redis.BasicRedisClientManager.#ctor(System.Collections.Generic.IEnumerable{System.String},System.Collections.Generic.IEnumerable{System.String})">
<summary>
Hosts can be an IP Address or Hostname in the format: host[:port]
e.g. 127.0.0.1:6379
default is: localhost:6379
</summary>
<param name="readWriteHosts">The write hosts.</param>
<param name="readOnlyHosts">The read hosts.</param>
</member>
<member name="M:ServiceStack.Redis.BasicRedisClientManager.GetClient">
<summary>
Returns a Read/Write client (The default) using the hosts defined in ReadWriteHosts
</summary>
<returns></returns>
</member>
<member name="M:ServiceStack.Redis.BasicRedisClientManager.GetReadOnlyClient">
<summary>
Returns a ReadOnly client using the hosts defined in ReadOnlyHosts.
</summary>
<returns></returns>
</member>
<member name="P:ServiceStack.Redis.BasicRedisClientManager.NamespacePrefix">
<summary>
Gets or sets object key prefix.
</summary>
</member>
<member name="T:ServiceStack.Redis.BufferPool">
<summary>
Courtesy of @marcgravell
http://code.google.com/p/protobuf-net/source/browse/trunk/protobuf-net/BufferPool.cs
</summary>
</member>
<member name="T:ServiceStack.Redis.Generic.QueuedRedisTypedCommand`1">
<summary>
A complete redis command, with method to send command, receive response, and run callback on success or failure
</summary>
</member>
<member name="T:ServiceStack.Redis.Generic.RedisTypedClient`1">
<summary>
Allows you to get Redis value operations to operate against POCO types.
</summary>
<typeparam name="T"></typeparam>
</member>
<member name="M:ServiceStack.Redis.Generic.RedisTypedClient`1.#ctor(ServiceStack.Redis.RedisClient)">
<summary>
Use this to share the same redis connection with another
</summary>
<param name="client">The client.</param>
</member>
<member name="T:ServiceStack.Redis.RedisTypedPipeline`1">
<summary>
Pipeline for redis typed client
</summary>
<typeparam name="T"></typeparam>
</member>
<member name="T:ServiceStack.Redis.Generic.RedisTypedCommandQueue`1">
<summary>
Queue of commands for redis typed client
</summary>
<typeparam name="T"></typeparam>
</member>
<member name="T:ServiceStack.Redis.RedisQueueCompletableOperation">
<summary>
Redis operation (transaction/pipeline) that allows queued commands to be completed
</summary>
</member>
<member name="T:ServiceStack.Redis.Messaging.RedisMqHost">
<summary>
Creates an MQ Host that processes all messages on a single background thread.
i.e. If you register 3 handlers it will only create 1 background thread.
The same background thread that listens to the Redis MQ Subscription for new messages
also cycles through each registered handler processing all pending messages one-at-a-time:
first in the message PriorityQ, then in the normal message InQ.
The Start/Stop methods are idempotent i.e. It's safe to call them repeatedly on multiple threads
and the Redis MQ Host will only have Started/Stopped once.
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqHost.ReplyClientFactory">
<summary>
Inject your own Reply Client Factory to handle custom Message.ReplyTo urls.
</summary>
</member>
<member name="T:ServiceStack.Redis.Messaging.RedisMqServer">
<summary>
Creates a Redis MQ Server that processes each message on its own background thread.
i.e. if you register 3 handlers it will create 7 background threads:
- 1 listening to the Redis MQ Subscription, getting notified of each new message
- 3x1 Normal InQ for each message handler
- 3x1 PriorityQ for each message handler
When RedisMqServer Starts it creates a background thread subscribed to the Redis MQ Topic that
listens for new incoming messages. It also starts 2 background threads for each message type:
- 1 for processing the services Priority Queue and 1 processing the services normal Inbox Queue.
Priority Queue's can be enabled on a message-per-message basis by specifying types in the
OnlyEnablePriortyQueuesForTypes property. The DisableAllPriorityQueues property disables all Queues.
The Start/Stop methods are idempotent i.e. It's safe to call them repeatedly on multiple threads
and the Redis MQ Server will only have Started or Stopped once.
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.RequestFilter">
<summary>
Execute global transformation or custom logic before a request is processed.
Must be thread-safe.
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.ResponseFilter">
<summary>
Execute global transformation or custom logic on the response.
Must be thread-safe.
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.ErrorHandler">
<summary>
Execute global error handler logic. Must be thread-safe.
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.PriortyQueuesWhitelist">
<summary>
If you only want to enable priority queue handlers (and threads) for specific msg types
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.DisablePriorityQueues">
<summary>
Don't listen on any Priority Queues
</summary>
</member>
<member name="P:ServiceStack.Redis.Messaging.RedisMqServer.PublishResponsesWhitelist">
<summary>
Opt-in to only publish responses on this white list.
Publishes all responses by default.
</summary>
</member>
<member name="M:ServiceStack.Redis.RedisClientManagerCacheClient.Dispose">
<sum
- 1
- 2
- 3
前往页