> -----Original Message-----
> From: Craig R. McClanahan [SMTP:[EMAIL PROTECTED]]
>
> Ted Neward wrote:
>
> > I thought the idea *was* to integrate them somehow.
> >
>
> Integration of the Tomcat servlet engine (from JSWDK) and Apache is going
> to
> happen within the auspices of the Jakarta project
> (http://jakarta.apache.org)
> once the source code is released. There will be an Apache module that
> connects
> to the servlet container, similar in concept to the way that Apache JServ
> connects today, so that separate port numbers will not be needed (from the
> end
> user's perspective). The JSWDK stuff will also continue to run
> stand-alone as
> it currently does, so you won't have to install a web server for
> development,
> or to deploy apps that do not need the web server features.
>
What I am thinking of does not expose separate port #'s to the end
user either. I've decided that I can create an Apache module that can pipe
requests/responses to/from the JSWDK server. I'll run the JSWDK server as
127.0.0.1:8001, this won't expose the JSWDK server to the outside world,
only processes on the web server machine will be able to talk to the JSWDK
server.
I've checked out the JServ Apache module (mod_jserv) and it is very
cool in that it supports "pluggable" protocols. It looks like maybe I can
just create a new protocol module for mod_jserv that communicates with the
JSWDK server and pretty much have what I need.
ted stockwell
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
