On Thu, Feb 2, 2012 at 12:41 PM, Rick Richardson
<rick.richardson@gmail.com> wrote:
> Right.  So I'm basically doing just that,  I've made an
>
[...]
>
> I am working on a module called redis_route which is an upstream
> patterned after rr
> This executes a subrequest to /servers which returns a Redis List of
> uris. I then parse those
> URIs and put them into an array which is then accessed when the
> upstream->peer.get callback is called requesting a new server.
> I store the rest, so if that backend uri fails, upstream->peer.get
> will be called for the next one on the list.
>
> Does this make sense?
>

Hmm, can we make the UI a bit more generic? We can surely fetch our
peer list from backends other than redis, like mysql, postgresql,
memcached, and etc etc etc ;)

Regards,
-agentzh

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel