>> 3. I need the replacement and changing of these proxies to be as >> dynamic as possible
>Don't quite get what the requirement is here... care to give a few >examples what you refer to by "as dynamic as possible". What I meant by this was the ability to change the list of parents, if possible dynamically, say by reading a new set of parents, from a file or list specified somewhere, in the event that one or more of the existing parents goes offline. This is also necessary if I need to maintain the parent list, without having to always modify the squid.conf file. I also would like to know the full syntax of specifying an acl that the contents should be read from a file, instead of listing each entry on the line. This will aid me in specifying my always_direct websites. -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Monday, October 27, 2003 7:49 PM To: Adeoye Oke Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] Routing to multiple Parent proxies On Mon, 27 Oct 2003, Adeoye Oke wrote: > The constraints I have to work with are: > 1. The parent proxies do not support ICP queries So you need prefer_direct off or never_direct. > 2. Some of the proxies become really slow, so I would need to send > requests to the faster proxies first. For this you basically need ICP. Alternatively it might be possible to extend Squid with some statistics trying to measure the "slowness" of a parent HTTP proxy to mostly avoid very slow parents, but this is also heavily depending on the sites and content accessed and not so easy to get correct. > 3. I need the replacement and changing of these proxies to be as > dynamic as possible Don't quite get what the requirement is here... care to give a few examples what you refer to by "as dynamic as possible". Regards Henrik
