Dossy said: > I don't see any downside to supporting Java, Java Servlets and JSP > better within AOLserver, and folks who do use Java-based technologies > have a lot to gain. Maybe there is something I do not understand about nsjk2, but how dows it make AOLserver "support" Java? As far as I can tell, it is realy only a fancy proxy to Tomcat, which in turn delivers finished, generated HTML or whatever other content type. Not very usefull as the only way to, in that case, web-enable some Java enterprise app using AOLserver would be to, well, bypass AOLserver. And by doing so make all the Tcl libraries and ADP templates I have written to make the rest of the site look the way it does useless.
> As long as Java support in AOLserver stays as an optional module, what's > the risk? It allows more people to use AOLserver, and that's a win-win > for everyone. Of course, fair enough if people want it. They want it for Apache, so why not for AOLserver. I just think to be able to say "AOLserver supports Java", you'd need a little more than the current nsjk2 effort. Cheers, Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
