GOMEZ Henri wrote:
> 
> Ouf, finished the renaming of jk2 (native2)
> 
> Some remarks :
> 
> 1) I choose to rename ALL JK directive since there are
>    just too many which are common in JK (SSL, LOG, DATE...)
> 
> ...
> 
>     AP_INIT_TAKE1(
>         "Jk2WorkersFile", jk2_set1, "workerFile", RSRC_CONF,
>         "the name of a worker file for the Jakarta servlet containers"),
>     AP_INIT_TAKE1(
>         "Jk2Properties", jk2_set1,  "workerFile", RSRC_CONF,
>         "Properties file containing additional settings ( replaces JkWoprkerFile )"),
>     AP_INIT_TAKE2(
>         "Jk2Set", jk2_set2, NULL, RSRC_CONF,
>         "Set a jk property, same syntax and rules as in JkWorkersFile"),
>     AP_INIT_TAKE2(
>         "Jk2Mount", jk2_set2, "mount", RSRC_CONF,
>         "A mount point from a context to a Tomcat worker"),
>     AP_INIT_TAKE2(
>         "Jk2Worker", jk2_setWorker, NULL, RSRC_CONF,
>         "Defines workers and worker properties "),
>     AP_INIT_TAKE2(
>         "Jk2Webapp", jk2_setWebapp, NULL, ACCESS_CONF,
>         "Defines a webapp in a Location directive and it's properties"),
>     AP_INIT_TAKE2(
>         "Jk2Servlet", jk2_setServlet, NULL, ACCESS_CONF,
>         "Defines a servlet in a Location directive"),
>     AP_INIT_TAKE1(
>         "Jk2MountCopy", jk2_set1, "root_apps_are_global", RSRC_CONF,
>         "Should the base server mounts be copied from main server to the virtual 
>server"),
>     AP_INIT_TAKE1(
>         "Jk2LogFile", jk2_set1, "logFile", RSRC_CONF,
>         "Full path to the Jakarta Tomcat module log file"),
>     AP_INIT_TAKE1(
>         "Jk2LogLevel", jk2_set1, "logLevel", RSRC_CONF,
>         "The Jakarta Tomcat module log level, can be debug, "
>         "info, error or emerg"),
>     AP_INIT_TAKE1(
>         "Jk2LogStampFormat", jk2_set1, "logStampFormat", RSRC_CONF,
>         "The Jakarta Tomcat module log format, follow strftime synthax"),
>     AP_INIT_TAKE1(
>         "Jk2HTTPSIndicator", jk2_set1, "HttpsIndicator", RSRC_CONF,
>         "Name of the Apache environment that contains SSL indication"),
>     AP_INIT_TAKE1(
>         "Jk2CERTSIndicator", jk2_set1, "CertsIndicator", RSRC_CONF,
>         "Name of the Apache environment that contains SSL client certificates"),
>     AP_INIT_TAKE1(
>          "Jk2CIPHERIndicator", jk2_set1, "CipherIndicator", RSRC_CONF,
>         "Name of the Apache environment that contains SSL client cipher"),
>     AP_INIT_TAKE1(
>         "Jk2SESSIONIndicator", jk2_set1, "SessionIndicator", RSRC_CONF,
>         "Name of the Apache environment that contains SSL session"),
>     AP_INIT_TAKE1(
>         "Jk2KEYSIZEIndicator", jk2_set1, "KeySizeIndicator", RSRC_CONF,
>         "Name of the Apache environment that contains SSL key size in use"),
>     AP_INIT_TAKE1(
>         "Jk2ExtractSSL", jk2_set1, "extractSsl", RSRC_CONF,
>         "Turns on SSL processing and information gathering by mod_jk"),
>     AP_INIT_TAKE1(
>         "Jk2ForwardSSLKeySize", jk2_set1, "forwardSslKeySize", RSRC_CONF,
>         "Forward SSL Key Size, to follow 2.3 specs but may broke old TC 3.2,"
>         "off is backward compatible"),
>     AP_INIT_TAKE1(
>         "ForwardURICompat",  jk2_set1, "forwardUriCompat", RSRC_CONF,
>         "Forward URI normally, less spec compliant but mod_rewrite compatible (old 
>TC)"),
>     AP_INIT_TAKE1(
>         "Jk2ForwardURICompatUnparsed", jk2_set1, "forwardUriCompatUnparsed", 
>RSRC_CONF,
>         "Forward URI as unparsed, spec compliant but broke mod_rewrite (old TC)"),
>     AP_INIT_TAKE1(
>         "Jk2ForwardURIEscaped", jk2_set1, "forwardUriEscaped", RSRC_CONF,
>         "Forward URI escaped and Tomcat (3.3 rc2) stuff will do the decoding part"),
>     AP_INIT_TAKE2(
>         "Jk2EnvVar", jk2_set2, "env", RSRC_CONF,
>         "Adds a name of environment variable that should be sent from web server "
>         "to servlet-engine"),
> 

Well I am not sure that changing the directive names serves any other purpose
that preventing using the old mod_jk configuration.

> ...
> 
> 2) When you have on Apache 2.0, mod_jk (native) and mod_jk2 (native2), both
>    report in error log as mod_jk/1.2.0 !
> 
> [Wed Feb 20 00:19:28 2002] [notice] Apache/2.0.28 (Unix) mod_ssl/3.0a0 
>OpenSSL/0.9.6b DAV/2 mod_jk/1.2.0 mod_jk/1.2.0 configured -- resuming normal 
>operations


mod_jk/2.0.0 sounds better.

> 
> 3) To have both installed you should rename mod_jk.so from native2 to mod_jk2.so
>    for example in apache lib.
> 
> So ....
> 
> - Why not rename mod_jk in native2 to mod_jk2.

No because we are already in jakarta-tomcat-connectors/jk (mod_jk2 does not
bring more information than native2).

> 
> - All directives are now Jk2...
> 
> - mod_jk2 start at version 1.0.0
> 
> JF, Costin, Kevin, Mike, Remy (;), thanks to comments
> 
> -
> Henri Gomez                 ___[_]____
> EMAIL : [EMAIL PROTECTED]        (. .)
> PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
> 
>   --------------------------------------------------------------------------------
>                               Name: jk2_renaming.diff.gz
>    jk2_renaming.diff.gz       Type: diff files (text/plain)
>                           Encoding: base64
>                        Description: jk2_renaming.diff.gz
> 
>   --------------------------------------------------------------------------------
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to