Return-Path: 
 <httpclient-dev-return-10621-apmail-jakarta-httpclient-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org
Received: (qmail 97168 invoked from network); 23 Feb 2005 16:31:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 23 Feb 2005 16:31:51 -0000
Received: (qmail 7232 invoked by uid 500); 23 Feb 2005 16:31:50 -0000
Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org
Received: (qmail 7201 invoked by uid 500); 23 Feb 2005 16:31:49 -0000
Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:httpclient-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:httpclient-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:httpclient-dev-help@jakarta.apache.org>
List-Post: <mailto:httpclient-dev@jakarta.apache.org>
List-Id: "HttpClient Project" <httpclient-dev.jakarta.apache.org>
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
Delivered-To: mailing list httpclient-dev@jakarta.apache.org
Received: (qmail 7183 invoked by uid 99); 23 Feb 2005 16:31:49 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from inspo8501.gs.com (HELO inspo8501.gs.com) (204.4.182.106)
  by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 23 Feb 2005 08:31:47 -0800
Received: from insvsod01.inz.gs.com (unknown [207.17.36.78])
	by inspo8501.gs.com (Postfix) with ESMTP id 5C83A245A2
	for <httpclient-dev@jakarta.apache.org>;
 Wed, 23 Feb 2005 11:31:45 -0500 (EST)
Received: from gsnmp08es.firmwide.corp.gs.com (gsnmp08es.firmwide.corp.gs.com
 [148.86.105.241]) by insvsod01.inz.gs.com with ESMTP for
 httpclient-dev@jakarta.apache.org; Wed, 23 Feb 2005 11:31:44 -0500
Received: by gsnmp08es.firmwide.corp.gs.com with Internet Mail Service
 (5.5.2657.72)
	id <FA9J34LC>; Wed, 23 Feb 2005 11:31:44 -0500
Message-Id: 
 <9CFD7198D93C6441932CA80CA30D26611BD687C8@gsnmp08es.firmwide.corp.gs.com>
From: "Rezaei, Mohammad A." <mohammad.rezaei@gs.com>
To: 'HttpClient Project' <httpclient-dev@jakarta.apache.org>
Subject: Delaying headers when Expect-Continue not set
Date: Wed, 23 Feb 2005 11:31:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

In HttpMethodBase, the http headers are flushed before the content is
written. Is there any reason for this other than Expect-Continue handling?
The reason I ask is that for small POST requests, this generates twice as
many network packets as necessary. If this is just for Expect-Continue
handling, would it be possible to move the flush inside the handling code?
That is, 

        // make sure the status line and headers have been sent
        conn.flushRequestOutputStream();

Moves into the if statement:

        if ((expectvalue != null) 
         && (expectvalue.compareToIgnoreCase("100-continue") == 0)) {
            if (ver.greaterEquals(HttpVersion.HTTP_1_1)) {

Thanks
Moh


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org