Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 14 Feb 2008 06:37:02 -0500
Subject: Re: ping for http in mod_proxy
From: "Akins, Brian" <Brian.Akins@turner.com>
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Message-ID: <C3D9920E.A6CCC%Brian.Akins@turner.com>
Thread-Topic: ping for http in mod_proxy
Thread-Index: Achua7RPFQuSl3f4TduHMTM8laqWxAAkjYvG
In-Reply-To: <5A6CB924-EC13-442A-8FEC-AD6918FB9A5D@jaguNET.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 2/13/08 1:09 PM, "Jim Jagielski" <jim@jaguNET.com> wrote:

> And again, we're basically doubling traffic and adding
> overheard (more overhead than AJP's cping/cpong) at which
> point I go back into wondering whether this sort of
> implementation makes sense at all...


So is the main issue we are trying to solve is that we have a keepalive
connection to an origin but it does away (closes) before we make or next
request and this causes an "error." (Sorry if I'm behind on the thread.)
Shouldn't the HTTP client handle all of this?  I know that libcurl handles
this situations very well - it just tries to reconnect.  How does serf
handle it?  

-- 
Brian Akins
Chief Operations Engineer
Turner Digital Media Technologies