On 5/4/2010 3:14 PM, Jeff Trawick wrote: > On Tue, May 4, 2010 at 4:04 PM, Jeff Trawick <traw...@gmail.com> wrote: >> On Tue, May 4, 2010 at 4:00 PM, Jeff Trawick <traw...@gmail.com> wrote: >>> On Tue, May 4, 2010 at 3:16 PM, William A. Rowe Jr. <wr...@rowe-clan.net> >>> wrote: > >>>> The solution, I believe, is to provide the mutex >>>> directive for all developers to use, and simply not adopt it within httpd >>>> itself >>>> until our jump to 2.4 happens. >> >> If mod_mutex gets added to 2.2, I'd suggest a nuance to this "not adopt" >> stance: >> >> If the httpd-bundled module currently has no mutex configuration and >> it is necessary to solve some operational problem, go ahead and use >> the mod_mutex feature. But for mod_ssl and others that already >> provide configuration, leave it as-is. > > suggestion withdrawn as it would be a required migration step for > users of the module, even if they don't have a mutex configuration > requirement (stepping away from the computer now)
Yea - I never intended this to replace any of 2.2's existing mutexes. Now, if mod_wizbang is backported (becoming less and less likely to be accepted), then it should be backported with a mod_mutex dependency, rather than developing the dual code paths of 2.3 vs 2.2. Consistency is helpful, and they are going to add the new directive to their 2.2 configuration whether it is WizbangMutex or just Mutex. Since nobody ever added a WizbangMutex directive before, this isn't a hardship. I'll recommend that our next releases of mod_ftp and mod_fcgid rely on this solution, be bumped by their version minor, and with the changes noted in the readme. This simplifies both modules code, and the minor bump of the *module* version level will signify to users that syntax/behavior is changing. I suppose we could include mod_mutex itself in the mod_ftp/mod_fcgid packaging to simplify things for the 2.2/2.0 user, if we wanted to. I do expect to still tag at least one more 2.0 release, sometime in the near future, and as we get towards 2.4 GA we would jettison 2.0 completely. Again, the ftp and fcgid modules are good examples of why this module becomes useful, and the code remains easier to maintain. It also allows a user to adopt 2.3-beta modules in their existing 2.2 or 2.0 installations with much less hassle. The more early testing of 2.3 in the real world, the better.
