First of all.thanks for your advice.
> B. Adjust the ICAP service to store information about "sessions" in
> a way that different service instances can share it. For example, if
> ICAP services run on the same machine, they can use shared memory
> segments to exchange information among each other.
I have no ability to achieve that different ICAP servers share same memory.
> A. Define "session" in HTTP or Squid terms that Squid understands.
> ACLs (likely including an external ACL or an eCAP adapter) that will
> define a "session" for any given transaction and annotate same-session
> transactions accordingly. Load balance based on sessions instead of
> random events. The same external ACL or eCAP adapter can define load
> balancing by annotating the transaction according to the ICAP service
> should be directed to.
I see your point,but I didn't find what I wanted in ACLs. i would like to
achieve load balancing based on IP（maybe implement by Source IP hash
algorithm）.Do you have a idea.
And,If one ICAP sever go down, can squid check it is down and will not send
message to it
Thanks in advance
View this message in context:
Sent from the Squid - Users mailing list archive at Nabble.com.
squid-users mailing list