On Sat, 2007-03-03 at 21:26 -0600, William A. Rowe, Jr. wrote:
> Mladen Turk wrote:
> > Not even that. We are talking for more then a year for
> > a next generation binary http(s) protocol.
> >
> > Almost everyone agreed that we need
> > at least few things:
> > 1. Encryption
> > 2. Variable sized
Mladen Turk wrote:
> Not even that. We are talking for more then a year for
> a next generation binary http(s) protocol.
>
> Almost everyone agreed that we need
> at least few things:
> 1. Encryption
> 2. Variable sized messages
> 3. Client connection close notification.
Talk about a hijaak :)
I
William A. Rowe, Jr. wrote:
Since JK2 is now off the map, does it make sense to update
Not even that. We are talking for more then a year for
a next generation binary http(s) protocol.
Almost everyone agreed that we need
at least few things:
1. Encryption
2. Variable sized messages
3. Client
William A. Rowe, Jr. wrote:
Since JK2 is now off the map, does it make sense to update
http://www.apache.org/dist/tomcat/tomcat-connectors/
and simply remove jk2? The user could still dig these up if they
wanted over at
http://archive.apache.org/dist/tomcat/tomcat-connectors/
Done I have
Yes I agree, that it's time for this. We could also remove mod_jk2 from
the download page and add a text line saying, that mod_jk2 is deprecated
and is only available from the archive (which itself has a link on that
page).
William A. Rowe, Jr. schrieb:
> Since JK2 is now off the map, does it make
Since JK2 is now off the map, does it make sense to update
http://www.apache.org/dist/tomcat/tomcat-connectors/
and simply remove jk2? The user could still dig these up if they
wanted over at
http://archive.apache.org/dist/tomcat/tomcat-connectors/
-
