Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of flyaruu@gmail.com designates
 209.85.210.192 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;
        b=wbRsNa2gfQOsRoyGPx6AJCEAjwDq8zcIm38qjyuYf0h9WkA0zN4D7UGGHbkI5A/pSw
         1ulMFjk2C8xXS4SbO2LnW2N7DC2zkk6kTOQdzd2syUQHeePjulrqtxUQwmEjVi9VslF2
         GjOsYrw7c5Sem3tjqaTliGAvIq6f1Fq5yzhvU=
MIME-Version: 1.0
In-Reply-To: <4BCD5116.6080601@ice-sa.com>
References: <y2ydb3c86751004192313z582b2b37re62ef3e907b4a564@mail.gmail.com>
	 <4BCD5116.6080601@ice-sa.com>
Date: Tue, 20 Apr 2010 09:35:38 +0200
Message-ID: <q2pdb3c86751004200035n2477e9e4g13fbc097216e45b4@mail.gmail.com>
Subject: Re: Missing events in Comet
From: Frank  Lyaruu <flyaruu@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=0016e6460744be68510484a61f67

--0016e6460744be68510484a61f67
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Andre,

Thanks for your reply.
Yes, it does. I am using a very basic java client (using a HttpURLConnectio=
n),
and I tested it against a server socket, and I always get a final, empty
chunk.

regards Frank.

ps. I am seeing this both on Tomcat 6.0.26 and Tomcat 7 trunk.

2010/4/20 Andr=E9 Warnier <aw@ice-sa.com>

> Frank Lyaruu wrote:
>
>> Hi all,
>>
>> We are trying to use Comet to make our web-service platform more resiste=
nt
>> to heavy loads.
>> We use HTTP/1.1 POSTS to send our requests (using chunked requests), and
>> the
>> client waits for the response.
>>
>> My problem is the following: As far as I can see, I have no way of
>> (reliably) detecting the end of the request.
>> I sometimes receive an END event, and sometimes a READ event with 0
>> available bytes. Those seem to indicate
>> that the request is complete, but sometimes I just get a few regular REA=
D
>> events and then nothing.
>>
>> If I don't use chunking, I can get it to work, as I just 'know' how many
>> bytes to expect. If I could do the de-chunking
>> myself I could also detect the final empty chunk + CRLF  to know the
>> request
>> is done.
>>
>> My question is: Shouldn't the final chunk always fire an END event, or a=
t
>> least an empty READ event?
>>
>> I hope someone can help me, I can supply all sorts of concise testing
>> code.
>>
>>  Have you verified that /the client/ does the chunking properly ?
> As far as I recall, it /must/ send a last chunk of size zero to indicate
> the end of the request, but does it, always ?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--0016e6460744be68510484a61f67--