You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Deepak J <dj...@verisign.com> on 2007/10/01 12:41:18 UTC
Comet Event handling unclear
I have developed a simple servlet that implements the CometProcessor and logs
"Begin Event Received", "Read Event Recieved" or "End Event received" as
might be the case.
My client program opens an HttpUrlConnection to do a POST, sets "Connection:
Close", and writes data that is approx 160KB. I then does a
connection.connect() and closes the connetion after a 200.
I would have expected to see 1 BEGIN event log, 1 or more READ event logs
and 1 END event log in the server.
I am running Tomcat 6.0.14/ Java 1.5 on Redhat Linux. I am using the
connector "org.apache.coyote.http11.Http11NioProtocol' with its default
settings.
So when I run my client program I recieve 2 being events and 2 read events
and no end event.
Can someone explain this behaviour? Does the connector need to be tweeked to
use NIO effectively in the scenario?
--
View this message in context: http://www.nabble.com/Comet-Event-handling-unclear-tf4547504.html#a12976844
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Comet Event handling unclear
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
you should receive one BEGIN event per connection, one READ event per
connection, and you wont receive end or error until the client or server
closes the connection or times out
Filip
Deepak J wrote:
> I have developed a simple servlet that implements the CometProcessor and logs
> "Begin Event Received", "Read Event Recieved" or "End Event received" as
> might be the case.
> My client program opens an HttpUrlConnection to do a POST, sets "Connection:
> Close", and writes data that is approx 160KB. I then does a
> connection.connect() and closes the connetion after a 200.
> I would have expected to see 1 BEGIN event log, 1 or more READ event logs
> and 1 END event log in the server.
> I am running Tomcat 6.0.14/ Java 1.5 on Redhat Linux. I am using the
> connector "org.apache.coyote.http11.Http11NioProtocol' with its default
> settings.
> So when I run my client program I recieve 2 being events and 2 read events
> and no end event.
> Can someone explain this behaviour? Does the connector need to be tweeked to
> use NIO effectively in the scenario?
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org