Yoav Shapira wrote:
I too vote both, and the classical style as well. Besides Costin's reasoning, with which I largely agree, I have also been seeing more and more people use Java web servers as the front-end, no less. And I want to keep the 100% pure Java option available, preferably as the default, even if it's a few percentage points worse performance.
Right, but even now, it's 100% pure Java. Highperformance (APR) is enabled by the installation of the needed native libraries, so I don't see the need for refactoring. If Costing thinks the exiting code needs refactoring, well, we have SVN, so he can create a branch and offer a better solution. Then we can discuss and (eventually vote) for inclusion in head.
On a related note, we can add a server-highperformance.xml configuration file that ships with Tomcat, and uses APR and whatever else we can think of to increase perfdormance out of the box. This is similar to the multiple httpd-XXX.conf files that ship with the HTTP web server.
Sure, the proper example would be fine. Even the server-openssl.xml too, etc... Regards, Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
