Filip Hanik - Dev Lists wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
I have noted that nothing has happened in tomcat/connectors/trunk/jk3.
Nearly 2 months without real road map nor clear specifications, what
is wrong?
I don't think anything is wrong. We are waiting for the list of
requirements, and any suggestion from yours or anybody else side
is more then welcome.
Comet support, that means, keep the connection open to receive/send data
in either direction.
Able to turn off buffering, so that data can get transferred directly
during Comet connections.
That's one that I know people would like to see
I understand we're talking about the native side here. My opinion on
this is it's not an absolute necessity, as most of the time the proxy
server will have not much to do except handling the connection, so it
should be able to dedicate the necessary threads. Of course, except for
specialized event based web servers, it's not possible to get rid of the
thread/process per request, so there's a large feasibility issue.
On the Java side, I plan to adapt the o.a.coyote.ajp package to support
comet and save threads in Tomcat, which is easy to do since the
connector structure is the same as HTTP (actually, it's simpler). I will
do it when the API and code gets really stable for the HTTP connector.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
