Tomcat could also decide to push config data, or context
status, etc.
Ok, we could have a little overhead (network latency) during
this init
phase but it's not a big problem since it's not too common.
Which make
me think that in multithreaded env like Apache 2.0 we could avoid to
redo
On Fri, 14 Dec 2001, GOMEZ Henri wrote:
Did there is plan to put the init stuff in shared area to avoid
multithreaded web-server do the full stage of autoconf.
We need to first figure out how to exchange info between apache processes.
The config will be saved in the workerEnv, uriMap, etc -
I'm getting close with jk2, there are just few more details I need to
resolve ( and then test, update the other server adapters, test again,
etc).
One change I'm making to get the things cleaner refers to the login and
discovery protocol.
Instead of a RPC-style, where Apache sends a command and
On Thu, 13 Dec 2001, GOMEZ Henri wrote:
Tomcat could also decide to push config data, or context status, etc.
Ok, we could have a little overhead (network latency) during this init
phase but it's not a big problem since it's not too common. Which make
me think that in multithreaded env like
I'm getting close with jk2, there are just few more details I need to
resolve ( and then test, update the other server adapters, test again,
etc).
One change I'm making to get the things cleaner refers to the login and
discovery protocol.
Instead of a RPC-style, where Apache sends a command and
