<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div> </div>
<div> </div>
<div> </div>
<div>On Tue, Jan 14, 2014, at 12:49 AM, Pedro Melo wrote:<br></div>
<blockquote type="cite"><div dir="ltr">Hi,<div><div> </div>
<div><div>On Tue, Jan 14, 2014 at 8:29 AM, Damien Krotkine <span dir="ltr"><<a href="mailto:damien@krotkine.com" target="_blank">damien@krotkine.com</a>></span> wrote:<br></div>
<div> </div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Jan 13, 2014, at 11:19 PM, Steffen Mueller wrote:> and a<br></div>
<div>
> question: My abstraction was to have a Sentinel*s* (plural) object. You<br></div>
<div>
> now have a Sentinel (singular) object. And that's how the code actually<br></div>
<div>
> works. The singular allows you to just subclass. I'm not sure how that<br></div>
<div>
> works with some of the logic that relies on knowing about all sentinels<br></div>
<div>
> rather than just the one you're connected to. I suppose that's owned by<br></div>
<div>
> the top level Redis object?<br></div>
<div> </div>
<div>Yes, the list of sentinels for the service is just an ArrayRef in the<br></div>
<div>
Redis instance. It gets updated when a sentinel is reached, and<br></div>
<div>
informations about linked sentinels can be retrieved. I didn't feel the<br></div>
<div>
need of having a class to represent the sentinels list, but I welcome<br></div>
<div>
counter arguments on that<br></div>
</blockquote><div> </div>
<div>I think that for now it would be good enough, you only want to know where to connect to. But if you plan on using this code to implement a client for the cluster, then it's not enough.<br></div>
<div> </div>
<div>With cluster you'll need multiple connections in parallel, and distribute the calls over them. It will evolve more into a ArrayRef of Redis object I think.<br></div>
</div>
</div>
</div>
</blockquote><div dir="ltr"><div><div><div> </div>
<div>I don't expect the code to evolve into a cluster client. I thought that we could devote the Redis::Cluster namespace to it. But for now I don't know anything about Redis Cluster, so ... :)</div>
<div> </div>
</div>
</div>
</div>
<blockquote type="cite"><div dir="ltr"><div><div><div> </div>
<div>Bye,<br></div>
</div>
<div>
-- <br></div>
<div>Pedro Melo<br></div>
<div>@pedromelo<br></div>
<div><a href="http://www.simplicidade.org/" target="_blank">http://www.simplicidade.org/</a><br></div>
<div><a href="mailto:xmpp%3Amelo@simplicidade.org" target="_blank">xmpp:melo@simplicidade.org</a><br></div>
<div>
mailto:<a href="mailto:melo@simplicidade.org" target="_blank">melo@simplicidade.org</a>
<br></div>
</div>
</div>
<div><u>_______________________________________________</u><br></div>
<div>Redis mailing list<br></div>
<div><a href="mailto:Redis@lists.scsys.co.uk">Redis@lists.scsys.co.uk</a><br></div>
<div><a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/redis">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/redis</a><br></div>
</blockquote></body>
</html>