--------------------- PatchSet 6349 Date: 2004/11/19 09:38:13 Author: oliv3 Branch: icap-2_5 Tag: (none) Log: High-availability patch from Members: src/cf.data.pre:1.49.2.33.2.22->1.49.2.33.2.23 Index: squid/src/cf.data.pre =================================================================== RCS file: /cvsroot/squid-sf//squid/src/cf.data.pre,v retrieving revision 1.49.2.33.2.22 retrieving revision 1.49.2.33.2.23 diff -u -r1.49.2.33.2.22 -r1.49.2.33.2.23 --- squid/src/cf.data.pre 27 Oct 2004 08:20:46 -0000 1.49.2.33.2.22 +++ squid/src/cf.data.pre 19 Nov 2004 09:38:13 -0000 1.49.2.33.2.23 @@ -1,6 +1,6 @@ # -# $Id: cf.data.pre,v 1.49.2.33.2.22 2004/10/27 08:20:46 oliv3 Exp $ +# $Id: cf.data.pre,v 1.49.2.33.2.23 2004/11/19 09:38:13 oliv3 Exp $ # # # SQUID Web Proxy Cache http://www.squid-cache.org/ @@ -2741,9 +2741,18 @@ Note: reqmod_precache and respmod_postcache is not yet implemented + Load-balancing and high availability: + You can obtain load-balancing and high availability by defining a + named service with different definitions. Then, the client + loops through the different entities of the service providing + load-balancing. If an entity is marked as unreachable, the client goes + one step further to the next entity: you have the high-availability. + See the service_1 definition below + Example: icap_service service_1 reqmod_precache 0 icap://icap1.mydomain.net:1344/reqmod -icap_service service_2 respmod_precache 0 icap://icap2.mydomain.net:1344/respmod +icap_service service_1 reqmod_precache 0 icap://icap2.mydomain.net:1344/reqmod +icap_service service_2 respmod_precache 0 icap://icap3.mydomain.net:1344/respmod DOC_END NAME: icap_class