Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: pass (nike.apache.org: domain of ming.zym@gmail.com designates
 209.85.160.42 as permitted sender)
Message-ID: <1351506134.26326.23.camel@zym6400>
Subject: prepare for the parent config revolution
From: "ming.zym@gmail.com" <ming.zym@gmail.com>
To: users@trafficserver.apache.org
Date: Mon, 29 Oct 2012 18:22:14 +0800
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

hi, all
  I think the parent proxy in parent.config will be a good solution for
cache system sibling, when you runing complex content network. If you
need the parent fuction, please help me understand what's your need, and
what you'd like the parent to be.

Currently I am thinking of making some change in the way the parent
works. We are thinking of the following requirements:

1, add 'Weight' for each parent host, then we can control the traffic
for each parent.
2, add 'Priority' for each parent host, then we get two or more parents
responsible for each 'Priority', for high availability 
3, merge DNS SRV into parent, and make SRV in parent only or parent
configurable.

thanks


-- 
Zhao Yongming
aka: zym @ apache.org, yonghao @ taobao.com