Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates
 74.125.83.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=hesD/c2wrs0SlIM9pTG+T4SntXUA6pRp2m09F2mUKUALghB+Mv6jxrE8bqM61sZkzr
         VmmJKBeD+sPDrYblaZfac14yHysMHNqYQ8Ss10GIUHaAmn7WpIv7N2gcb8ScXnCAUu0c
         971zJyArO4+zPvFPAswWKBsPdZVQKjMWGCMvU=
MIME-Version: 1.0
In-Reply-To: <BANLkTim+DyO1V8sG53BNNKPinQhXr6898Q@mail.gmail.com>
References: <BANLkTi=8om1NytbNrfSM7j-4v-oyfOs_eA@mail.gmail.com>
	<99B7EA1BC7D04A23A7CF60533DCDDD31@rabbithill>
	<BANLkTi=6BbWSKGrAd=a3cK=H3+L2BPD2ZQ@mail.gmail.com>
	<E077FEE8E09B448D87FC0E1FC5431E73@rabbithill>
	<E5C8E6D40ED04E888E46BF13A6D43B98@rabbithill>
	<BANLkTimNXfordBsJQmLKCJn93xeT_7iNrw@mail.gmail.com>
	<3AEF44764A564DDEA5E93118E87E369F@rabbithill>
	<D5EEACB044D94D71A8BB366D22AE68F8@rabbithill>
	<BANLkTint6mnnuBBUq9ZtSCT3YLv3qj+KBA@mail.gmail.com>
	<4DEBB657.5030205@rowe-clan.net>
	<BANLkTi=a9iKo0=un1q0DyChbpXWs47Jtig@mail.gmail.com>
	<4DEBC800.1020707@rowe-clan.net>
	<BANLkTi=1vJXansMkhwBpFvGQb7BusihPfA@mail.gmail.com>
	<4DEBDEE3.9040007@rowe-clan.net>
	<BANLkTi=mUtAtzeuimU+NDTgtTO8C32wUxQ@mail.gmail.com>
	<BANLkTikW49hDzVKtjsMENWv2S+HcYcKpPA@mail.gmail.com>
	<BANLkTim+DyO1V8sG53BNNKPinQhXr6898Q@mail.gmail.com>
Date: Sun, 5 Jun 2011 17:51:49 -0400
Message-ID: <BANLkTintJFNHy2zNu9Lw-aW+kX7QnCEK-w@mail.gmail.com>
From: Eric Covener <covener@gmail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [users@httpd] mod_deflate and chunked encoding

On Sun, Jun 5, 2011 at 5:40 PM, Xavier Noria <fxn@hashref.com> wrote:
> On Sun, Jun 5, 2011 at 11:36 PM, Eric Covener <covener@gmail.com> wrote:
>
>>> If Passenger has to dechunk, and we want a chunked compressed
>>> response, and Apache is the one responsible for doing that, how should
>>> we signal Apache that we want compression and streaming for that
>>> particular response.
>>
>> This is the main path of just configuring mod_deflate. =A0Nothing else
>> required. =A0Only passenger cares how passenger decided what the content
>> of the response was, to everyone else it's just buckets of data.
>>
>> "Streaming" just means the module that generates the content of the
>> response routinely hands some data off to Apache to send off to the
>> client rather then e.g. waiting until it's 100% done. =A0It's also not
>> something you need to configure.
>
> But there has to be something else, because in streaming I want a
> chunked response that should start sending chunks to the client as
> soon as possible.
>
> If the back server sent just 200 bytes in the first chunk, I want
> those 200 bytes compressed and forwarded to the client exactly now. In
> particular there's no Content-Length computed.

Does passenger pass the first 200 bytes to Apache?

Does it follow them with a "flush bucket"?

Does the protocol passenger uses on the backend allow your app to tell
it when to flush?

Does the result change when you turn on mod_deflate (the preceding
questions are probably best asked on a passenger list, with this final
questions answer in-hand)

--=20
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org