mod_jserv/3955: Need to run the JServ engine as a separate thread

[John Kirkley <jo...@groveware.com>]

>Number:         3955
>Category:       mod_jserv
>Synopsis:       Need to run the JServ engine as a separate thread
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Feb 23 18:40:00 PST 1999
>Last-Modified:
>Originator:     john@groveware.com
>Organization:
apache
>Release:        Apache-JServ-1.0b3
>Environment:
Linux, Solaris and NT	
>Description:
We are hoping to use JServ as the web server side of an application.  
There is database and general code that our servlets must have access to
and that must be initialized in the JVM that runs the JServ engine.  
Unfortuanately since JServ runs as a thread from main,  doing this
sort of thing is inconvenient.  What would be ideal is to make
JServ implement Runnable and put the socket listening stuff inside
of the run() method.   That way we  could run the JServ engine as another
thread inside of our application, and I think this is in general a better
design since it is more flexible.   As it is now I have hacked the JServ
class to do as I have stated and it works fine, but it would be much
better if this was part of the actual distribution.
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]