e good job...
Christophe
-Message d'origine-
De : Remy Maucherat [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 janvier 2007 14:48
À : Tomcat Developers List
Objet : Re: Comet API and InputStream.available()
Christophe Pierret wrote:
Here is what I understood:
Assumption #1: ==
EMAIL PROTECTED]
Envoyé : mercredi 24 janvier 2007 14:48
À : Tomcat Developers List
Objet : Re: Comet API and InputStream.available()
Christophe Pierret wrote:
> Here is what I understood:
>
> Assumption #1: When you receive a
> CometEvent.EventType.READ event, you can
Christophe Pierret wrote:
Here is what I understood:
Assumption #1: When you receive a
CometEvent.EventType.READ event, you can always read() at least one
byte from the request's InputStream without blocking.
Is this correct ? If not correct, then this mail goes directly to
tra
k - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : mardi 23 janvier 2007 18:14
À : Tomcat Developers List
Objet : Re: Comet API and InputStream.available()
ok, I'm confused, why would available return 1 when there is no data to be read?
the values for available are
>0 data to be read
0 no
ok, I'm confused, why would available return 1 when there is no data to
be read?
the values for available are
>0 data to be read
0 no data to be read
-1 end of stream reached
I don't think we have -1 in our values, as that would only happen if the
client closed the connection, and at that point
