Re: Parent AND neighbour?

>>>Pete Philips said:
 --> It just occured to me that it would be useful to be able to specify
 --> a site as both a neighbour and a parent so that it is a neighbour for
 --> all queries and a parent just for queries to a certain domain.
 -->
 --> I have looked at the cache_host_domain tag but can't see how to do it.
 -->
 --> Example.
 -->
 --> cache_host 1.2.3.4 neighbour 3128 3130
 --> cache_host 1.2.3.4 parent 3128 3130
 --> cache_host_domain 1.2.3.4 .edu

It would be more concise if all information about a neighbor would be
within a single line, such as

cache_host a.b.c.d neighbor 3128 8080 .edu (0.5) .com (.3)

with the number in brackets being just the weights. To dream on, I would love to
stumble over an mSQL patch where I can write

  MsqlNeighborhood mymsqlhost mycachedb "select IP, ICPport, HTTPport from caches"

Also, I could imagine the addition of "child" and "asymetric neighbors".

"Child" entries have purely documentary character for squid. For statistic
programs which derive figures like "helpfulness to neighbors, children"
this would be a good source.

"Asymmetric neighboring" we (ISP) use in situations when we peer with
reseller ISPs which have leased lines to us. "Parenting" would
cause *every* traffic going through our proxy (too much), "Symmetric
neighboring" would imply that the much smaller neighbor would be
asked too much. Asymmetric neighboring is the optimal choice for both.

</DREAM>

\rho

-- 
  ___  | mailto:rho@Austria.EU.net
 / _ \ | Affil: EUnet Austria, Internet Provider
| |_) )| http://www.Austria.EU.net/
|  __/ | phone:+43-(1)-313-76    fax:+43-(1)-310-69-26
\ \    
/_/