On 14.09.2010 08:11, Mladen Turk wrote:
On 09/13/2010 11:38 PM, Rainer Jung wrote:
I have the impression there is not enough dev time available at the
moment for bigger things like migrating it to APR, but a switch to 1.3
would allow us to formulate a clear message (some incompatibilities,
partially dropped support and a couple of new
features).
+1.
Roll 1.2.31 as last 1.2.x release and
declare trunk as 1.3.x with deprecated connectors removed.
Hehe, the radicals. I'd say: we don't intend to add more features to
1.2.x. We still support it but since it is pretty stable we don't expect
much release activity.
Declaring it "final" before even the first 1.3.x release seems a bit
strong ;)
Not so sure for nsapi thought, cause that web server
is still developed and I'd like to keep it maintained.
All right. Should we indicate, that the NSAPI support lacks some of the
features? Most of the features that have been added e.g. via Jk...
directives have not been ported to NSAPI. Everything that can be
expressed via workers.properties is fine, but the things that need
configuration integration into the web server itself haven't been ported.
(Well at least for as long as the Oracle is giving it for free).
:)
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
