I doubt it works properly with the HttpUrlConnection, its better if you
use a socket connection, as you have no idea how the underlying
implementation works in HttpUrlConnection
Filip
Peter Warren wrote:
Hi Filip,
Somehow I missed your response a while back. Below are two test clients
and o
Hi Filip,
Somehow I missed your response a while back. Below are two test clients
and one comet servlet. One client works, and the other doesn't. I
found out the failing client doesn't work because HttpURLConnection
doesn't seem to allow writing to the output stream after the input
stream has b
why don't you make your test available, I'll run it through
Filip
Peter Warren wrote:
Yes, I'm using the NIO connector. Here is the config line from my
server.xml:
Are there any other configuration options I need to set?
Peter
Filip Hanik - Dev Lists wrote:
and you are using the A
Yes, I'm using the NIO connector. Here is the config line from my
server.xml:
Are there any other configuration options I need to set?
Peter
Filip Hanik - Dev Lists wrote:
> and you are using the APR or the NIO connector right?
>
> Filip
>
> Peter Warren wrote:
>> Thanks for the suggestio
and you are using the APR or the NIO connector right?
Filip
Peter Warren wrote:
Thanks for the suggestion. I changed the comet test servlet to read
directly from the input stream as shown in the advanced io example. I'm
still seeing the same behavior. No comet read event gets generated on
th
Thanks for the suggestion. I changed the comet test servlet to read
directly from the input stream as shown in the advanced io example. I'm
still seeing the same behavior. No comet read event gets generated on
the server, only the begin event which contains the client's first
message. The clien
On 5/23/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
take a look at the documentation, the way you are reading it is incorrect.
you need to take advantage of the available() method
With a reader, it's ready().
Rémy
take a look at the documentation, the way you are reading it is incorrect.
you need to take advantage of the available() method
Filip
Peter Warren wrote:
My BEGIN block in my comet servlet now looks like the code below (added
a while loop to read until the buffer is empty). Is that what you ha
Hi,
I think you have to add
cometEvent.getHttpServletResponse().getWriter().flush();
also in the READ event case.
Matthias
> -Original Message-
> From: Peter Warren [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 22, 2007 10:11 PM
> To: users@tomcat.apache.org
> Subject: comet read eve
it could be because the data from the request already came in with the
request.
when the BEGIN happens, perform the actions as if there was a READ as
well, ie, empty out the buffer.
Filip
Peter Warren wrote:
The following client code generates a comet BEGIN event on the server
but not a subse
10 matches
Mail list logo
