sol myr wrote:
Thanks :)
You're correct about blocking inputStreams, but I actually need Tomcat to write
a multipart *response*, on an OutputStream (the reading side is on the client,
and our client-side programmers will manage it without blocking).
I wondered whether I'll have to hand-code it
(manually output the headers,
etc), or is there some utilities on Tomcat/apach.
Thanks anyway :)
--- On Tue, 1/4/11, Filip Hanik - Dev Lists wrote:
From: Filip Hanik - Dev Lists
Subject: Re: Comet and multipart
To: "Tomcat Users List"
Date: Tuesday, January 4, 2011, 9:43 AM
> 1) If
on how long the Comet request is alive
best
Filip
Thanks again
--- On Mon, 1/3/11, Filip Hanik - Dev Lists wrote:
From: Filip Hanik - Dev Lists
Subject: Re: Comet and multipart
To: "Tomcat Users List"
Date: Monday, January 3, 2011, 8:47 AM
On 1/3/2011 7:48 AM, sol myr wrote:
Hi,
on, 1/3/11, Filip Hanik - Dev Lists wrote:
From: Filip Hanik - Dev Lists
Subject: Re: Comet and multipart
To: "Tomcat Users List"
Date: Monday, January 3, 2011, 8:47 AM
On 1/3/2011 7:48 AM, sol myr wrote:
> Hi,
>
> We're implementing a CometServlet on top of Tomcat NIO conn
On 1/3/2011 7:48 AM, sol myr wrote:
Hi,
We're implementing a CometServlet on top of Tomcat NIO connector, using "long
polling".
Currently we're using the approach recommended by most tutorials: the client
opens a connection and waits for a message (for a configured timeout); if such
a message
On 03/01/2011 14:48, sol myr wrote:
> Hi,
>
> We're implementing a CometServlet on top of Tomcat NIO connector, using "long
> polling".
> Currently we're using the approach recommended by most tutorials: the client
> opens a connection and waits for a message (for a configured timeout); if
> su
Hi,
We're implementing a CometServlet on top of Tomcat NIO connector, using "long
polling".
Currently we're using the approach recommended by most tutorials: the client
opens a connection and waits for a message (for a configured timeout); if such
a message arrives, the client consumes it (e.g.
