Hey, Why not chaining Varnish with HAProxy? Your varnish has a single way out, HAProxy. Then in HAProxy you can either use_backend or use-server that can be combined with any type of layer 7 information to take routing decision. This routing decision can take their logic from a raw text file you can update with a basic script (needs a haproxy reload of course)
my 2 cents :) Baptiste On Thu, Dec 13, 2012 at 6:26 PM, J David <[email protected]> wrote: > > > On Mon, Dec 10, 2012 at 4:50 AM, Per Buer <[email protected]> > wrote: >>> >>> Is there an efficient way to approach this? >> >> >> Currently I think the most efficient approach would be the DNS director. > > > Unfortunately, we used to use a DNS-based approach with squid. It's > efficient enough on the proxy-cache side, but maintaining the zone files in > BIND is problematic as the number of records involved becomes large and the > frequency of updated becomes high. > > Thanks for the response! > > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
