~ Do you know enough about Tomcat's chunking implementation
to write a patch (I certainly do not)?
Nope. I wish I did though...
--Keyur
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Keyur,
>
> On 8/6/2009 12:35 PM, Keyur Sh
I agree with Chris and I also appreciate Michael's dilemma.
While headers can never be added as headers once the response is committed,
the trailer headers are in fact encoded in the body itself.
So the convention could be that if a user has specified certain trailer
headers: response.setHeader
#x27;m
>> trying to
>> avoid. With a large number of concurrent users, the buffering is proving
>> to
>> be a performance bottleneck and is causing frequent GC sweeps.
>>
>> I think what I'm trying to do with the Trailer header is valid http usage
>>
http usage
(correct me if that's wrong). And I was hoping tomcat supports this usage.
--Keyur
Filip Hanik - Dev Lists wrote:
>
> On 08/05/2009 02:14 PM, Keyur Shah wrote:
>> Tomcat by default sends chunked responses => Transfer-Encoding:chunked
>>
>> I'm calculati
Tomcat by default sends chunked responses => Transfer-Encoding:chunked
I'm calculating the ETag for the response dynamically as the content is
being
written to the response stream. Since I'll know the final value of the ETag
only
when the stream is closed, I indicate that using the Trailer header
