diff --git a/GMW/GMW.csproj b/GMW/GMW.csproj
index 65d0d9e4..d6778d67 100644
--- a/GMW/GMW.csproj
+++ b/GMW/GMW.csproj
@@ -278,8 +278,8 @@
..\packages\StackExchange.Redis.1.2.4\lib\net46\StackExchange.Redis.dll
-
- ..\packages\StackExchange.Redis.StrongName.1.2.4\lib\net46\StackExchange.Redis.StrongName.dll
+
+ ..\packages\StackExchange.Redis.StrongName.1.2.3\lib\net46\StackExchange.Redis.StrongName.dll
diff --git a/GMW/Web.config b/GMW/Web.config
index 1db4bb83..1c7e9e36 100644
--- a/GMW/Web.config
+++ b/GMW/Web.config
@@ -239,7 +239,7 @@
-
+
diff --git a/GMW/packages.config b/GMW/packages.config
index fd1fdb86..abad4599 100644
--- a/GMW/packages.config
+++ b/GMW/packages.config
@@ -27,7 +27,7 @@
-
+
\ No newline at end of file
diff --git a/packages/StackExchange.Redis.StrongName.1.2.3/StackExchange.Redis.StrongName.1.2.3.nupkg b/packages/StackExchange.Redis.StrongName.1.2.3/StackExchange.Redis.StrongName.1.2.3.nupkg
new file mode 100644
index 00000000..bdba4408
Binary files /dev/null and b/packages/StackExchange.Redis.StrongName.1.2.3/StackExchange.Redis.StrongName.1.2.3.nupkg differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.dll
new file mode 100644
index 00000000..e6ee2d63
Binary files /dev/null and b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.dll differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.xml b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.xml
similarity index 98%
rename from packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.xml
rename to packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.xml
index 68930694..ee98df08 100644
--- a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.xml
+++ b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net45/StackExchange.Redis.StrongName.xml
@@ -1467,6 +1467,26 @@
By default this may do a sweep for dead profiling contexts, you can disable this by passing "allowCleanupSweep: false".
+
+
+ Gets how many result-box instances were allocated
+
+
+
+
+ Gets how many async completion workers were queueud
+
+
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
The type of a connection
@@ -1487,6 +1507,702 @@
A subscriber connection recieves unsolicted messages from the server as pub/sub events occur
+
+
+ Provides configuration controls of a redis server
+
+
+
+
+ Show what is in the pending (unsent) queue
+
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Break the connection without mercy or thought
+
+
+
+
+ DEBUG SEGFAULT performs an invalid memory access that crashes Redis. It is used to simulate bugs during the development.
+
+ http://redis.io/commands/debug-segfault
+
+
+
+ CLIENT PAUSE is a connections control command able to suspend all the Redis clients for the specified amount of time (in milliseconds).
+
+ http://redis.io/commands/client-pause
+
+
+
+ Gets the cluster configuration associated with this server, if known
+
+
+
+
+ Gets the address of the connected server
+
+
+
+
+ Gets the features available to the connected server
+
+
+
+
+ Gets whether the connection to the server is active and usable
+
+
+
+
+ Gets whether the connected server is a replica / slave
+
+
+
+
+ Explicitly opt in for slave writes on writable slaves
+
+
+
+
+ Gets the operating mode of the connected server
+
+
+
+
+ Gets the version of the connected server
+
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Get summary statistics associates with this server
+
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Promote the selected node to be master
+
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+ Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
+ http://redis.io/commands/shutdown
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Show the state and info of the specified master.
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Ask the server to close the connection. The connection is closed as soon as all pending replies have been written to the client.
+
+ http://redis.io/commands/quit
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Gets the multiplexer that created this instance
+
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout), reporting which
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for the given asynchronous operations to complete (or timeout)
+
+
+
+
+ A SocketManager monitors multiple sockets for availability of data; this is done using
+ the Socket.Select API and a dedicated reader-thread, which allows for fast responses
+ even when the system is under ambient load.
+
+
+
+
+ Completion type for BeginConnect call
+
+
+
+
+ Creates a new (optionally named) SocketManager instance
+
+
+
+
+ Creates a new SocketManager instance
+
+
+
+
+ Gets the name of this SocketManager instance
+
+
+
+
+ Releases all resources associated with this instance
+
+
+
+
+ Allows callbacks from SocketManager as work is discovered
+
+
+
+
+ Indicates that a socket has connected
+
+
+
+
+ Indicates that the socket has signalled an error condition
+
+
+
+
+ Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
+
+
+
+
+ Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
+
+
+
+
+ Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
+
+
+
+
+ This writes a message **directly** to the output stream; note
+ that this ignores the queue, so should only be used *either*
+ from the regular dequeue loop, *or* from the "I've just
+ connected" handshake (when there is no dequeue loop) - otherwise,
+ you can pretty much assume you're going to destroy the stream
+
+
Completion type for CompletionTypeHelper
@@ -2011,6 +2727,16 @@
Represents the abstract multiplexer API
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
Gets the client-name that will be used on all new connections
@@ -4460,18 +5186,6 @@
The number of times reconnect retries have already been made by the multiplexer while it was in connecting state
Total time elapsed in milliseconds since the last reconnect retry was made
-
-
- Common operations available to all redis connections
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
Represents a resumable, cursor-based scanning operation
@@ -4492,563 +5206,6 @@
The offset into the current page
-
-
- Common operations available to all redis connections
-
-
-
-
- Gets the multiplexer that created this instance
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
-
-
- Wait for a given asynchronous operation to complete (or timeout), reporting which
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for the given asynchronous operations to complete (or timeout)
-
-
-
-
- Provides configuration controls of a redis server
-
-
-
-
- Gets the cluster configuration associated with this server, if known
-
-
-
-
- Gets the address of the connected server
-
-
-
-
- Gets the features available to the connected server
-
-
-
-
- Gets whether the connection to the server is active and usable
-
-
-
-
- Gets whether the connected server is a replica / slave
-
-
-
-
- Explicitly opt in for slave writes on writable slaves
-
-
-
-
- Gets the operating mode of the connected server
-
-
-
-
- Gets the version of the connected server
-
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Get summary statistics associates with this server
-
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Promote the selected node to be master
-
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
- Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
- http://redis.io/commands/shutdown
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Show the state and info of the specified master.
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
A redis connection used as the subscriber in a pub/sub scenario
@@ -5408,11 +5565,6 @@
3: it disables non-pref logging, as it is usually server-targeted
-
-
- Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
-
-
Additional options for the MIGRATE command
@@ -5448,15 +5600,6 @@
Ordered from high values to low values
-
-
- This writes a message **directly** to the output stream; note
- that this ignores the queue, so should only be used *either*
- from the regular dequeue loop, *or* from the "I've just
- connected" handshake (when there is no dequeue loop) - otherwise,
- you can pretty much assume you're going to destroy the stream
-
-
Big ol' wrapper around most of the profiling storage logic, 'cause it got too big to just live in ConnectionMultiplexer.
@@ -6457,58 +6600,6 @@
The data is persisted even if save points are NOT configured
-
-
- Allows callbacks from SocketManager as work is discovered
-
-
-
-
- Indicates that a socket has connected
-
-
-
-
- Indicates that the socket has signalled an error condition
-
-
-
-
- Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
-
-
-
-
- Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
-
-
-
-
- A SocketManager monitors multiple sockets for availability of data; this is done using
- the Socket.Select API and a dedicated reader-thread, which allows for fast responses
- even when the system is under ambient load.
-
-
-
-
- Creates a new (optionally named) SocketManager instance
-
-
-
-
- Creates a new SocketManager instance
-
-
-
-
- Gets the name of this SocketManager instance
-
-
-
-
- Releases all resources associated with this instance
-
-
Describes a sorted-set element with the corresponding value
diff --git a/packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.dll
new file mode 100644
index 00000000..dc860865
Binary files /dev/null and b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.dll differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.xml b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.xml
similarity index 98%
rename from packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.xml
rename to packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.xml
index 68930694..ee98df08 100644
--- a/packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.xml
+++ b/packages/StackExchange.Redis.StrongName.1.2.3/lib/net46/StackExchange.Redis.StrongName.xml
@@ -1467,6 +1467,26 @@
By default this may do a sweep for dead profiling contexts, you can disable this by passing "allowCleanupSweep: false".
+
+
+ Gets how many result-box instances were allocated
+
+
+
+
+ Gets how many async completion workers were queueud
+
+
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
The type of a connection
@@ -1487,6 +1507,702 @@
A subscriber connection recieves unsolicted messages from the server as pub/sub events occur
+
+
+ Provides configuration controls of a redis server
+
+
+
+
+ Show what is in the pending (unsent) queue
+
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Break the connection without mercy or thought
+
+
+
+
+ DEBUG SEGFAULT performs an invalid memory access that crashes Redis. It is used to simulate bugs during the development.
+
+ http://redis.io/commands/debug-segfault
+
+
+
+ CLIENT PAUSE is a connections control command able to suspend all the Redis clients for the specified amount of time (in milliseconds).
+
+ http://redis.io/commands/client-pause
+
+
+
+ Gets the cluster configuration associated with this server, if known
+
+
+
+
+ Gets the address of the connected server
+
+
+
+
+ Gets the features available to the connected server
+
+
+
+
+ Gets whether the connection to the server is active and usable
+
+
+
+
+ Gets whether the connected server is a replica / slave
+
+
+
+
+ Explicitly opt in for slave writes on writable slaves
+
+
+
+
+ Gets the operating mode of the connected server
+
+
+
+
+ Gets the version of the connected server
+
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Get summary statistics associates with this server
+
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Promote the selected node to be master
+
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+ Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
+ http://redis.io/commands/shutdown
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Show the state and info of the specified master.
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Ask the server to close the connection. The connection is closed as soon as all pending replies have been written to the client.
+
+ http://redis.io/commands/quit
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Gets the multiplexer that created this instance
+
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout), reporting which
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for the given asynchronous operations to complete (or timeout)
+
+
+
+
+ A SocketManager monitors multiple sockets for availability of data; this is done using
+ the Socket.Select API and a dedicated reader-thread, which allows for fast responses
+ even when the system is under ambient load.
+
+
+
+
+ Completion type for BeginConnect call
+
+
+
+
+ Creates a new (optionally named) SocketManager instance
+
+
+
+
+ Creates a new SocketManager instance
+
+
+
+
+ Gets the name of this SocketManager instance
+
+
+
+
+ Releases all resources associated with this instance
+
+
+
+
+ Allows callbacks from SocketManager as work is discovered
+
+
+
+
+ Indicates that a socket has connected
+
+
+
+
+ Indicates that the socket has signalled an error condition
+
+
+
+
+ Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
+
+
+
+
+ Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
+
+
+
+
+ Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
+
+
+
+
+ This writes a message **directly** to the output stream; note
+ that this ignores the queue, so should only be used *either*
+ from the regular dequeue loop, *or* from the "I've just
+ connected" handshake (when there is no dequeue loop) - otherwise,
+ you can pretty much assume you're going to destroy the stream
+
+
Completion type for CompletionTypeHelper
@@ -2011,6 +2727,16 @@
Represents the abstract multiplexer API
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
Gets the client-name that will be used on all new connections
@@ -4460,18 +5186,6 @@
The number of times reconnect retries have already been made by the multiplexer while it was in connecting state
Total time elapsed in milliseconds since the last reconnect retry was made
-
-
- Common operations available to all redis connections
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
Represents a resumable, cursor-based scanning operation
@@ -4492,563 +5206,6 @@
The offset into the current page
-
-
- Common operations available to all redis connections
-
-
-
-
- Gets the multiplexer that created this instance
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
-
-
- Wait for a given asynchronous operation to complete (or timeout), reporting which
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for the given asynchronous operations to complete (or timeout)
-
-
-
-
- Provides configuration controls of a redis server
-
-
-
-
- Gets the cluster configuration associated with this server, if known
-
-
-
-
- Gets the address of the connected server
-
-
-
-
- Gets the features available to the connected server
-
-
-
-
- Gets whether the connection to the server is active and usable
-
-
-
-
- Gets whether the connected server is a replica / slave
-
-
-
-
- Explicitly opt in for slave writes on writable slaves
-
-
-
-
- Gets the operating mode of the connected server
-
-
-
-
- Gets the version of the connected server
-
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Get summary statistics associates with this server
-
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Promote the selected node to be master
-
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
- Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
- http://redis.io/commands/shutdown
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Show the state and info of the specified master.
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
A redis connection used as the subscriber in a pub/sub scenario
@@ -5408,11 +5565,6 @@
3: it disables non-pref logging, as it is usually server-targeted
-
-
- Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
-
-
Additional options for the MIGRATE command
@@ -5448,15 +5600,6 @@
Ordered from high values to low values
-
-
- This writes a message **directly** to the output stream; note
- that this ignores the queue, so should only be used *either*
- from the regular dequeue loop, *or* from the "I've just
- connected" handshake (when there is no dequeue loop) - otherwise,
- you can pretty much assume you're going to destroy the stream
-
-
Big ol' wrapper around most of the profiling storage logic, 'cause it got too big to just live in ConnectionMultiplexer.
@@ -6457,58 +6600,6 @@
The data is persisted even if save points are NOT configured
-
-
- Allows callbacks from SocketManager as work is discovered
-
-
-
-
- Indicates that a socket has connected
-
-
-
-
- Indicates that the socket has signalled an error condition
-
-
-
-
- Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
-
-
-
-
- Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
-
-
-
-
- A SocketManager monitors multiple sockets for availability of data; this is done using
- the Socket.Select API and a dedicated reader-thread, which allows for fast responses
- even when the system is under ambient load.
-
-
-
-
- Creates a new (optionally named) SocketManager instance
-
-
-
-
- Creates a new SocketManager instance
-
-
-
-
- Gets the name of this SocketManager instance
-
-
-
-
- Releases all resources associated with this instance
-
-
Describes a sorted-set element with the corresponding value
diff --git a/packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.dll
new file mode 100644
index 00000000..b0d7c929
Binary files /dev/null and b/packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.dll differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.xml b/packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.xml
similarity index 98%
rename from packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.xml
rename to packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.xml
index 68930694..ee98df08 100644
--- a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.xml
+++ b/packages/StackExchange.Redis.StrongName.1.2.3/lib/netstandard1.5/StackExchange.Redis.StrongName.xml
@@ -1467,6 +1467,26 @@
By default this may do a sweep for dead profiling contexts, you can disable this by passing "allowCleanupSweep: false".
+
+
+ Gets how many result-box instances were allocated
+
+
+
+
+ Gets how many async completion workers were queueud
+
+
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
The type of a connection
@@ -1487,6 +1507,702 @@
A subscriber connection recieves unsolicted messages from the server as pub/sub events occur
+
+
+ Provides configuration controls of a redis server
+
+
+
+
+ Show what is in the pending (unsent) queue
+
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Get the value of key. If the key does not exist the special value nil is returned. An error is returned if the value stored at key is not a string, because GET only handles string values.
+
+ the value of key, or nil when key does not exist.
+ http://redis.io/commands/get
+
+
+
+ Break the connection without mercy or thought
+
+
+
+
+ DEBUG SEGFAULT performs an invalid memory access that crashes Redis. It is used to simulate bugs during the development.
+
+ http://redis.io/commands/debug-segfault
+
+
+
+ CLIENT PAUSE is a connections control command able to suspend all the Redis clients for the specified amount of time (in milliseconds).
+
+ http://redis.io/commands/client-pause
+
+
+
+ Gets the cluster configuration associated with this server, if known
+
+
+
+
+ Gets the address of the connected server
+
+
+
+
+ Gets the features available to the connected server
+
+
+
+
+ Gets whether the connection to the server is active and usable
+
+
+
+
+ Gets whether the connected server is a replica / slave
+
+
+
+
+ Explicitly opt in for slave writes on writable slaves
+
+
+
+
+ Gets the operating mode of the connected server
+
+
+
+
+ Gets the version of the connected server
+
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes a given client connection identified by ip:port.
+ The ip:port should match a line returned by the CLIENT LIST command.
+ Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
+
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT KILL command closes multiple connections that match the specified filters
+
+ the number of clients killed.
+ http://redis.io/commands/client-kill
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
+
+ http://redis.io/commands/client-list
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Obtains the current raw CLUSTER NODES output from a cluster server
+
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Get all configuration parameters matching the specified pattern.
+
+ All matching configuration parameters.
+ http://redis.io/commands/config-get
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ Resets the statistics reported by Redis using the INFO command.
+
+ http://redis.io/commands/config-resetstat
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
+
+ http://redis.io/commands/config-rewrite
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
+
+ http://redis.io/commands/config-set
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the number of keys in the database.
+
+ http://redis.io/commands/dbsize
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Return the same message passed in
+
+ http://redis.io/commands/echo
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of all databases on the server.
+
+ http://redis.io/commands/flushall
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Delete all the keys of the database.
+
+ http://redis.io/commands/flushdb
+
+
+
+ Get summary statistics associates with this server
+
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
+
+ http://redis.io/commands/info
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
+
+ Warning: consider KEYS as a command that should only be used in production environments with extreme care.
+ http://redis.io/commands/keys
+ http://redis.io/commands/scan
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
+
+ http://redis.io/commands/lastsave
+
+
+
+ Promote the selected node to be master
+
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Explicitly request the database to persist the current state to disk
+
+ http://redis.io/commands/bgrewriteaof
+ http://redis.io/commands/bgsave
+ http://redis.io/commands/save
+ http://redis.io/topics/persistence
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Inidicates whether the specified script is defined on the server
+
+
+
+
+ Inidicates whether the specified script hash is defined on the server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Removes all cached scripts on this server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+
+ Explicitly defines a script on the server
+
+
+
+ Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
+ http://redis.io/commands/shutdown
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
+
+ http://redis.io/commands/slaveof
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
+
+ http://redis.io/commands/slowlog
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
+
+ a list of active channels, optionally matching the specified pattern.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
+
+ the number of patterns all the clients are subscribed to.
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
+
+ http://redis.io/commands/pubsub
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ The TIME command returns the current server time.
+
+ The server's current time.
+ http://redis.io/commands/time
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Returns the ip and port number of the master with that name.
+ If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
+
+ the sentinel service name
+
+ the master ip and port
+ http://redis.io/topics/sentinel
+
+
+
+ Show the state and info of the specified master.
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ the master state as KeyValuePairs
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of monitored masters and their state.
+
+
+ an array of master state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Show a list of slaves for this master, and their state.
+
+ the sentinel service name
+
+ an array of slave state KeyValuePair arrays
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
+ (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
+
+ the sentinel service name
+
+ http://redis.io/topics/sentinel
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Ask the server to close the connection. The connection is closed as soon as all pending replies have been written to the client.
+
+ http://redis.io/commands/quit
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Common operations available to all redis connections
+
+
+
+
+ The CLIENT GETNAME returns the name of the current connection as set by CLIENT SETNAME. Since every new connection starts without an associated name, if no name was assigned a null string is returned.
+
+ http://redis.io/commands/client-getname
+ The connection name, or a null string if no name is set.
+
+
+
+ Gets the multiplexer that created this instance
+
+
+
+
+ This command is often used to test if a connection is still alive, or to measure latency.
+
+ The observed latency.
+ http://redis.io/commands/ping
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout), reporting which
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for a given asynchronous operation to complete (or timeout)
+
+
+
+
+ Wait for the given asynchronous operations to complete (or timeout)
+
+
+
+
+ A SocketManager monitors multiple sockets for availability of data; this is done using
+ the Socket.Select API and a dedicated reader-thread, which allows for fast responses
+ even when the system is under ambient load.
+
+
+
+
+ Completion type for BeginConnect call
+
+
+
+
+ Creates a new (optionally named) SocketManager instance
+
+
+
+
+ Creates a new SocketManager instance
+
+
+
+
+ Gets the name of this SocketManager instance
+
+
+
+
+ Releases all resources associated with this instance
+
+
+
+
+ Allows callbacks from SocketManager as work is discovered
+
+
+
+
+ Indicates that a socket has connected
+
+
+
+
+ Indicates that the socket has signalled an error condition
+
+
+
+
+ Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
+
+
+
+
+ Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
+
+
+
+
+ Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
+
+
+
+
+ This writes a message **directly** to the output stream; note
+ that this ignores the queue, so should only be used *either*
+ from the regular dequeue loop, *or* from the "I've just
+ connected" handshake (when there is no dequeue loop) - otherwise,
+ you can pretty much assume you're going to destroy the stream
+
+
Completion type for CompletionTypeHelper
@@ -2011,6 +2727,16 @@
Represents the abstract multiplexer API
+
+
+ For debugging; when not enabled, servers cannot connect
+
+
+
+
+ For debugging; when not enabled, end-connect is silently ignored (to simulate a long-running connect)
+
+
Gets the client-name that will be used on all new connections
@@ -4460,18 +5186,6 @@
The number of times reconnect retries have already been made by the multiplexer while it was in connecting state
Total time elapsed in milliseconds since the last reconnect retry was made
-
-
- Common operations available to all redis connections
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
Represents a resumable, cursor-based scanning operation
@@ -4492,563 +5206,6 @@
The offset into the current page
-
-
- Common operations available to all redis connections
-
-
-
-
- Gets the multiplexer that created this instance
-
-
-
-
- This command is often used to test if a connection is still alive, or to measure latency.
-
- The observed latency.
- http://redis.io/commands/ping
-
-
-
- Wait for a given asynchronous operation to complete (or timeout), reporting which
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for a given asynchronous operation to complete (or timeout)
-
-
-
-
- Wait for the given asynchronous operations to complete (or timeout)
-
-
-
-
- Provides configuration controls of a redis server
-
-
-
-
- Gets the cluster configuration associated with this server, if known
-
-
-
-
- Gets the address of the connected server
-
-
-
-
- Gets the features available to the connected server
-
-
-
-
- Gets whether the connection to the server is active and usable
-
-
-
-
- Gets whether the connected server is a replica / slave
-
-
-
-
- Explicitly opt in for slave writes on writable slaves
-
-
-
-
- Gets the operating mode of the connected server
-
-
-
-
- Gets the version of the connected server
-
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes a given client connection identified by ip:port.
- The ip:port should match a line returned by the CLIENT LIST command.
- Due to the single-treaded nature of Redis, it is not possible to kill a client connection while it is executing a command.From the client point of view, the connection can never be closed in the middle of the execution of a command.However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
-
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT KILL command closes multiple connections that match the specified filters
-
- the number of clients killed.
- http://redis.io/commands/client-kill
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- The CLIENT LIST command returns information and statistics about the client connections server in a mostly human readable format.
-
- http://redis.io/commands/client-list
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Obtains the current raw CLUSTER NODES output from a cluster server
-
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Get all configuration parameters matching the specified pattern.
-
- All matching configuration parameters.
- http://redis.io/commands/config-get
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- Resets the statistics reported by Redis using the INFO command.
-
- http://redis.io/commands/config-resetstat
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG REWRITE command rewrites the redis.conf file the server was started with, applying the minimal changes needed to make it reflecting the configuration currently used by the server, that may be different compared to the original one because of the use of the CONFIG SET command.
-
- http://redis.io/commands/config-rewrite
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- The CONFIG SET command is used in order to reconfigure the server at runtime without the need to restart Redis. You can change both trivial parameters or switch from one to another persistence option using this command.
-
- http://redis.io/commands/config-set
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the number of keys in the database.
-
- http://redis.io/commands/dbsize
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Return the same message passed in
-
- http://redis.io/commands/echo
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of all databases on the server.
-
- http://redis.io/commands/flushall
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Delete all the keys of the database.
-
- http://redis.io/commands/flushdb
-
-
-
- Get summary statistics associates with this server
-
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- The INFO command returns information and statistics about the server in a format that is simple to parse by computers and easy to read by humans.
-
- http://redis.io/commands/info
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Returns all keys matching pattern; the KEYS or SCAN commands will be used based on the server capabilities; note: to resume an iteration via cursor, cast the original enumerable or enumerator to IScanningCursor.
-
- Warning: consider KEYS as a command that should only be used in production environments with extreme care.
- http://redis.io/commands/keys
- http://redis.io/commands/scan
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Return the time of the last DB save executed with success. A client may check if a BGSAVE command succeeded reading the LASTSAVE value, then issuing a BGSAVE command and checking at regular intervals every N seconds if LASTSAVE changed.
-
- http://redis.io/commands/lastsave
-
-
-
- Promote the selected node to be master
-
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Explicitly request the database to persist the current state to disk
-
- http://redis.io/commands/bgrewriteaof
- http://redis.io/commands/bgsave
- http://redis.io/commands/save
- http://redis.io/topics/persistence
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Inidicates whether the specified script is defined on the server
-
-
-
-
- Inidicates whether the specified script hash is defined on the server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Removes all cached scripts on this server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
-
- Explicitly defines a script on the server
-
-
-
- Asks the redis server to shutdown, killing all connections. Please FULLY read the notes on the SHUTDOWN command.
- http://redis.io/commands/shutdown
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- The SLAVEOF command can change the replication settings of a slave on the fly. If a Redis server is already acting as slave, specifying a null master will turn off the replication, turning the Redis server into a MASTER. Specifying a non-null master will make the server a slave of another server listening at the specified hostname and port.
-
- http://redis.io/commands/slaveof
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- To read the slow log the SLOWLOG GET command is used, that returns every entry in the slow log. It is possible to return only the N most recent entries passing an additional argument to the command (for instance SLOWLOG GET 10).
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- You can reset the slow log using the SLOWLOG RESET command. Once deleted the information is lost forever.
-
- http://redis.io/commands/slowlog
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Lists the currently active channels. An active channel is a Pub/Sub channel with one ore more subscribers (not including clients subscribed to patterns).
-
- a list of active channels, optionally matching the specified pattern.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscriptions to patterns (that are performed using the PSUBSCRIBE command). Note that this is not just the count of clients subscribed to patterns but the total number of patterns all the clients are subscribed to.
-
- the number of patterns all the clients are subscribed to.
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- Returns the number of subscribers (not counting clients subscribed to patterns) for the specified channel.
-
- http://redis.io/commands/pubsub
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- The TIME command returns the current server time.
-
- The server's current time.
- http://redis.io/commands/time
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Returns the ip and port number of the master with that name.
- If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave.
-
- the sentinel service name
-
- the master ip and port
- http://redis.io/topics/sentinel
-
-
-
- Show the state and info of the specified master.
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- the master state as KeyValuePairs
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of monitored masters and their state.
-
-
- an array of master state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Show a list of slaves for this master, and their state.
-
- the sentinel service name
-
- an array of slave state KeyValuePair arrays
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
-
-
- Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels
- (however a new version of the configuration will be published so that the other Sentinels will update their configurations).
-
- the sentinel service name
-
- http://redis.io/topics/sentinel
-
A redis connection used as the subscriber in a pub/sub scenario
@@ -5408,11 +5565,6 @@
3: it disables non-pref logging, as it is usually server-targeted
-
-
- Checks both high-pri and regular queues to see if the next item is a PING, and if so: dequeues it and returns it
-
-
Additional options for the MIGRATE command
@@ -5448,15 +5600,6 @@
Ordered from high values to low values
-
-
- This writes a message **directly** to the output stream; note
- that this ignores the queue, so should only be used *either*
- from the regular dequeue loop, *or* from the "I've just
- connected" handshake (when there is no dequeue loop) - otherwise,
- you can pretty much assume you're going to destroy the stream
-
-
Big ol' wrapper around most of the profiling storage logic, 'cause it got too big to just live in ConnectionMultiplexer.
@@ -6457,58 +6600,6 @@
The data is persisted even if save points are NOT configured
-
-
- Allows callbacks from SocketManager as work is discovered
-
-
-
-
- Indicates that a socket has connected
-
-
-
-
- Indicates that the socket has signalled an error condition
-
-
-
-
- Indicates that data is available on the socket, and that the consumer should read synchronously from the socket while there is data
-
-
-
-
- Indicates that we cannot know whether data is available, and that the consume should commence reading asynchronously
-
-
-
-
- A SocketManager monitors multiple sockets for availability of data; this is done using
- the Socket.Select API and a dedicated reader-thread, which allows for fast responses
- even when the system is under ambient load.
-
-
-
-
- Creates a new (optionally named) SocketManager instance
-
-
-
-
- Creates a new SocketManager instance
-
-
-
-
- Gets the name of this SocketManager instance
-
-
-
-
- Releases all resources associated with this instance
-
-
Describes a sorted-set element with the corresponding value
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/StackExchange.Redis.StrongName.1.2.4.nupkg b/packages/StackExchange.Redis.StrongName.1.2.4/StackExchange.Redis.StrongName.1.2.4.nupkg
deleted file mode 100644
index a5406f78..00000000
Binary files a/packages/StackExchange.Redis.StrongName.1.2.4/StackExchange.Redis.StrongName.1.2.4.nupkg and /dev/null differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.dll
deleted file mode 100644
index 3a59cabb..00000000
Binary files a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net45/StackExchange.Redis.StrongName.dll and /dev/null differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.dll
deleted file mode 100644
index e027f75d..00000000
Binary files a/packages/StackExchange.Redis.StrongName.1.2.4/lib/net46/StackExchange.Redis.StrongName.dll and /dev/null differ
diff --git a/packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.dll b/packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.dll
deleted file mode 100644
index 21cb5c2b..00000000
Binary files a/packages/StackExchange.Redis.StrongName.1.2.4/lib/netstandard1.5/StackExchange.Redis.StrongName.dll and /dev/null differ