FM / examples

/home/techb158/ileadtechnology.com/vendor/predis/predis/examples/

/home/techb158/ileadtechnology.com/vendor/predis/predis/examples

Name	Size	Mode	Actions
custom_cluster_distributor.php	2801	0644	edit dl rm
debuggable_connection.php	2352	0644	edit dl rm
dispatcher_loop.php	2166	0644	edit dl rm
executing_redis_commands.php	1464	0644	edit dl rm
key_prefixing.php	891	0644	edit dl rm
lua_scripting_abstraction.php	1721	0644	edit dl rm
monitor_consumer.php	1573	0644	edit dl rm
pipelining_commands.php	1006	0644	edit dl rm
pubsub_consumer.php	2033	0644	edit dl rm
redis_collections_iterators.php	2812	0644	edit dl rm
replication_complex.php	2617	0644	edit dl rm
replication_sentinel.php	2162	0644	edit dl rm
replication_simple.php	1767	0644	edit dl rm
session_handler.php	1893	0644	edit dl rm
shared.php	1025	0644	edit dl rm
transaction_using_cas.php	1542	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/vendor/predis/predis/examples/replication_sentinel.php (2162B)

<?php

/*
 * This file is part of the Predis package.
 *
 * (c) Daniele Alessandri <suppakilla@gmail.com>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

require __DIR__.'/shared.php';

// Predis supports redis-sentinel to provide high availability in master / slave
// scenarios. The only but relevant difference with a basic replication scenario
// is that sentinel servers can manage the master server and its slaves based on
// their state, which means that they are able to provide an authoritative and
// updated configuration to clients thus avoiding static configurations for the
// replication servers and their roles.

// Instead of connection parameters pointing to redis nodes, we provide a list
// of instances of redis-sentinel. Users should always provide a timeout value
// low enough to not hinder operations just in case a sentinel is unreachable
// but Predis uses a default value of 100 milliseconds for sentinel parameters
// without an explicit timeout value.
//
// NOTE: in real-world scenarios sentinels should be running on different hosts!
$sentinels = array(
    'tcp://127.0.0.1:5380?timeout=0.100',
    'tcp://127.0.0.1:5381?timeout=0.100',
    'tcp://127.0.0.1:5382?timeout=0.100',
);

$client = new Predis\Client($sentinels, array(
    'replication' => 'sentinel',
    'service' => 'mymaster',
));

// Read operation.
$exists = $client->exists('foo') ? 'yes' : 'no';
$current = $client->getConnection()->getCurrent()->getParameters();
echo "Does 'foo' exist on {$current->alias}? $exists.", PHP_EOL;

// Write operation.
$client->set('foo', 'bar');
$current = $client->getConnection()->getCurrent()->getParameters();
echo "Now 'foo' has been set to 'bar' on {$current->alias}!", PHP_EOL;

// Read operation.
$bar = $client->get('foo');
$current = $client->getConnection()->getCurrent()->getParameters();
echo "We fetched 'foo' from {$current->alias} and its value is '$bar'.", PHP_EOL;

/* OUTPUT:
Does 'foo' exist on slave-127.0.0.1:6381? yes.
Now 'foo' has been set to 'bar' on master!
We fetched 'foo' from master and its value is 'bar'.
*/

cmd: