Return-Path: 
 <tomcat-dev-return-6190-qmlist-jakarta-archive-tomcat-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 58379 invoked from network); 25 Feb 2002 16:45:30 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 25 Feb 2002 16:45:30 -0000
Received: (qmail 17987 invoked by uid 97); 25 Feb 2002 16:44:43 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org
Received: (qmail 17923 invoked by uid 97); 25 Feb 2002 16:44:43 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 17869 invoked from network); 25 Feb 2002 16:44:42 -0000
X-Authentication-Warning: localhost.localdomain: costinm owned process doing
 -bs
Date: Mon, 25 Feb 2002 07:28:49 -0800 (PST)
From: <costinm@covalent.net>
X-X-Sender: <costinm@dyn-62.sfo.covalent.net>
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: RE: Jk2 config 
In-Reply-To: <BBDCA5B56D25F843A025AE850BA70F06218300@css8.slib.com>
Message-ID: <Pine.LNX.4.33.0202250716180.4087-100000@dyn-62.sfo.covalent.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, 25 Feb 2002, GOMEZ Henri wrote:

> JkSet LogFile		"/var/log/httpd/mod_jk.log"

I would use logFile, logLevel - current options in 
workers.properties start will small caps, and this 
can go in either w.properties and httpd.conf.

> The forward options : ?
> 
> JkSet Forward SSLKeySize 
> JkSet Forward URICompat
> JkSet Forward URICompatUnparsed
> JkSet Forward URIEscaped

JkSet forward.SSLKeySize true

JkSet uriCompat true
JkSet uriCompatUnparsed true

Or even better:
JkSet sslKeySizeForward true
JkSet uriForward compat/compatUnparsed/escaped

> >JkMount is not doing anything special - it's the same 
> >efect as the properties file we use on IIS. Except that
> >properties are easier to generate and will be consistent
> >for all servers ( no longer need to generate 3 different 
> >styles ). 
> 
> -1, I'd like to keep the JkMount as it's absolutly mandatory
> for fine tuning (ie all examples servlet/jsp handled by TC) but
> static by Apache. It could be renamed to JkURIMount for example.

JkMount is replaced by:

urimap.properties 

or ( apache style )

<Location /examples >
  JkWebapp worker ajp13
</Location>

<Location /examples/*.jsl>
  JkHandler jakarta/jk2-servlet
</Location>

or 
JkSet /examples/*.jsp ajp13

We can add a 
JkUriSet /examples/*.jsp ajp13


> >3. JkServlet NAME VALUE
> >Set properties per/servlet. I'm not yet finished with
> >this one, we may not need it.
> 
> What's the planned use for this one ?

Set properties per/uri - fine tunning, including 
setting the servlet name - the URI is mapped once
by apache, there's no need for a second mapping 
in tomcat.

What about:

JkUriSet /uri name value

to replace both JkWebapp and JkServlet ?
Both are used to set properties associated with a uri -
the worker name for the webapp, fine tunning for uris.

> What about :
> 
> Jk(2)EnvVar ?
> Jk(2)MountCopy ?

JkSet mountCopy true 

JkSet env.NAME DEFAULT_FALUE

We could also use it in a <Location> context later

JkUriSet env.NAME VALUE 

In this particular case it may be worth adding a 
"JkEnv" directive, but it _must_ have an equivalent in
workers.properties and that means a JkSet equivalent too.

Costin 


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>