The updated draft with suggested changes attached below.

| >    5.1.    Interface Stability
| >
| >    mod_jk, mod_fcgi and mod_security can be considered to have the
| >    same interface stability of apache (i.e interface directives can
| >    change during releases.) since they are apache modules.
| 
| I don't think that reasoning makes sense... i.e. just because they are
| modules doesn't mean they must have the same stability as apache.
| 
| For example if you include mod_security 2.1.3, it is in theory
| possible that mod_security 2.1.4 could be completely incompatible
| with the rules supported by 2.1.3.
| 
| (In practice we know from the earlier thread that the intent is to
| keep it compatible, which is great.)
| 
| Instead of the above text in s.5.1, the case should have a summary (a
| short paragraph for each of the 3 modules should be good) of the
| earlier posts here describing the intended compatibility story for
| these 3 modules, so it gets recorded in the ARC case.
| 
| 
| >     These Apache modules imports interfaces from
| > 
| >     NAME                      STABILITY        NOTES
| 
| >     LDAP                       Uncommitted       PSARC/2000/362/
| >     SUNWlxml                   Uncommitted       PSARC/2001/175/
| 
| Those 2 don't seem correct. 2001/175 calls the API "Standard" and
| looks like in 2000/362 the public APIs are "Evolving".
                                    rahul
--
1. e4 _

-------------- next part --------------

Additional Apache Modules

13 December 2007

1.    Summary and motivation

    1.1.    Introduction

    This FastTrack delivers Apache modules mod_jk, mod_fcgid and
    mod_security to the Apache2 in OpenSolaris.

    Modules allow Apache to integrate and provide functionality
    during runtime that were not available during compile time.

    This project integrates the most recent stable releases of
    mod_jk[1] tomcat-connectors-1.2.25, mod_fcgid[2] 2.2 and
    mod_security[3] 2.1.3

    This case seeks Minor Release Binding.

2.    Technical issues

    2.1.    Key objects

    /usr/apache2/2.2/libexec/mod_jk.so
    /usr/apache2/2.2/libexec/mod_fcgid.so
    /usr/apache2/2.2/libexec/mod_security2.so

    /usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so
    /usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so
    /usr/apache2/2.2/libexec/${ISAINFO}/mod_security2.so

 
    2.2 Versioning

    mod_jk, mod_fcgid and mod_security have a single active release.
    (There was a module named mod_jk2 which was deprecated. It was not
    the successor to mod_jk.)

    It is not possible to query the modules to find out their
    versions.  The only way to do that is to look at the package
    description for the package including it.

    2.2 Directory Naming and Structure

    This project delivers the shared libraries of 32 bit and 64 bit
    into /usr/apache2/2.2/libexec and /usr/apache2/2.2/libexec/${ISAINFO}/ 
    directories of apache. This is in keeping with the approach taken
    by the Apache2 integration project for OpenSolaris (PSARC/2007/586).

3. Documentation

    The modules mod_jk, mod_fcgid and mod_security do not install
    documentation into apache though they come with some documentation
    in their source. The recommended way to access their documentation
    is to look at their websites (mod_fcgid[4] ,mod_jk[5] and
    mod_security[6]).

4. Packaging and Delivery

    The modules will be delivered under the cluster SUNCapch22m. This
    cluster consists of SUNWapch22m-fcgid, SUNWapch22m-jk and
    SUNWapch22m-security respectively.

5.  Interfaces

    5.1.    Interface Stability

    5.1.1 mod_jk
        The mod_jk developers will try to keep the releases of 1.2.X
    line compatible with each other. But this is not guaranteed in
    case of new features that may need to be retracted due to some
    bugs or vulnerabilities.

    5.1.2 mod_security
       The mod_security developers will keep the compatibility
    between releases of the same major number. (ie 2.y.z with 2 being
    the major number.) But there is no guarantee that meaning of a
    rule set (configuration directive) would be exactly the same
    across any two releases.

    5.1.3 mod_fcgid
       There were no commitments from mod_fcgid developers in this
    regard.

    5.2.    Imported Interfaces

    These Apache modules imports interfaces from

    NAME                      STABILITY        NOTES
    Apache2                    Uncommitted       PSARC/2007/586/   
    LDAP                       Evolving          PSARC/2000/362/
    PCRE                       Uncommitted       PSARC/2007/164/
    SUNWlxml                   Committed         PSARC/2001/175/

    5.3.    Exported Interfaces

    NAME                                                STABILITY
 
    /usr/apache2/2.2/libexec/mod_jk.so                  Uncommitted
    /usr/apache2/2.2/libexec/mod_fcgid.so               Uncommitted
    /usr/apache2/2.2/libexec/mod_security.so            Uncommitted
    /usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so       Uncommitted
    /usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so    Uncommitted
    /usr/apache2/2.2/libexec/${ISAINFO}/mod_security.so Uncommitted


6.    References

   1. http://fastcgi.coremail.cn/
   2. http://tomcat.apache.org/connectors-doc/
   3. http://www.modsecurity.org/projects/modsecurity/apache/index.html
   4. http://fastcgi.coremail.cn/doc.htm
   5. http://tomcat.apache.org/connectors-doc/generic_howto/quick.html
   6. http://www.modsecurity.org/documentation/index.html

Reply via email to