Seema Alevoor wrote: > Draft for the integration of APR and APR-util 1.3.2 and updation of Apache > 2.2 version to 2.2.9 > is at > http://wikis.sun.com/download/attachments/7077996/apache229-apr-apu132-arc-case-draft.txt > . > a few comments, mostly on stuff inherited from previous ARC cases
>Apache 2.2.9 ChangeLog can be found here: > http://apache.deathculture.net/httpd/CHANGES_2.2.9 canonical 2.2.9 change log location: http://www.apache.org/dist/httpd/CHANGES_2.2.9 (sounds better than "deathculture.net") 4. Apache Internationalization. Apache2 provides GNU iconv compatible I18N support via libaprutil-1.so.0.2.8. The integration proposed in this FastTrack relies on the GNU iconv compatibility layer available in Solaris' libc.so. libaprutil-1.so.0.2.8 won't be the new name ( ...0.3.2 ?) I'm curious of the meaning of "GNU iconv compatibility layer" in this context. Solaris has had iconv() for years and apr-util knows how to use it. (Solaris iconv() is perhaps one "const" away from GNU iconv() as far as apr-util knows, though code set names provided by the library are exposed to the end user and may differ.) 6.1. Interface Stability Compatibility between the minor release family of APR, APR-util canonical distribution is not guaranteed. We will classify APR, APR-util Interfaces as Uncommitted. I think we should promise as much as apr does, and regression test for that with frozen binaries and Apache modules. Otherwise third-party providers of binaries who bother to read the details may be disinclined to claim support for the web stack. (Recall that Solaris-provided 32-bit Apache 2.0 broke the ABI in a patch last year when enabling large file support in apr -- very painful for some customers using third-party modules for Apache.) apr won't remove interfaces until the major version changes. apr won't add interfaces until the minor version changes (more conservative than is usually necessary). What is this in terms of "Interface Stability" terminology? Nothing is said here about httpd interface stability. -/- Is there a separate document with considerations such as - which apr/httpd features [not] provided - which support libraries chosen and why (e.g., native LDAP vs. OpenLDAP, and implications for plugin modules) -- Jeff Trawick Sun Microsystems x60172/+1 919 882 6531
