Jeff Trawick wrote: > > Does any of this need to be covered in an ARC case? > > 1. A reference guide is now included: > > Presumably the reference guide will now be installed with the > OpenSolaris package SUNWapch22m-fcgid. > > /usr/apache2/2.2/manual/mod/mod_fcgid.html > /usr/apache2/2.2/manual/mod/mod_fcgid.html.en
Documentation written for human consumption (as opposed to programmatic) is not considered an interface. And the filesystem location already exists, so nothing new to declare here. > 2. Some directives which were allowed inside <VirtualHost ...> but > previously ignored there are processed differently now: > > a. Some are now respected inside <VirtualHost ...>. > b. The remainder are now rejected at startup when appearing inside > <VirtualHost ...>. Yes, those need to be documented. If there's a doc somewhere listing the details just point at it. > 3. I think this is making a mountain out of a molehill, but for > completeness: Bug fixes in the handling of inherited mod_fcgid > configuration (e.g., <VirtualHost ...> inheriting from the global > server, or <Directory /a/b/c> inheriting settings from <Directory /a/b>) > mean that existing configurations can work slightly differently in rare > circumstances. ... > mod_fcgid 2.2: Setting1 and Setting2 now have their default values for > files in directory /a/b/c. > mod_fcgid 2.3.4: Setting1 and Setting2 values are inherited from > <Directory /a/b>, Setting3 has value3. > > (The old behavior was not how any bundled Apache modules work.) It is a change that can conceivably break some customer somewhere so do document it. What you already wrote is plenty to explain it. > 4. While existing directive names are still respected, every directive > has a new, preferred name. Declare the old still-accepted ones as Obsolete and note the new ones with suitable interface stability. > The reference guide has a mapping table. Pointing to it is fine. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
