On Saturday 03 December 2011, William A. Rowe Jr. wrote: > On 12/3/2011 1:32 AM, Gregg L. Smith wrote: > > On 12/2/2011 3:48 PM, Stefan Fritsch wrote: > >> - the follwing modules added since 2.2 lack documentation > >> > >> - mod_socache_dbm > >> - mod_socache_memcache > >> - mod_socache_shmcb > > > > These are required for SSL AFIAK, they must stay! Mentioned in > > the mod_ssl docks should be sufficient IMHO. > > It isn't. Someone trimming their LoadModule lines will undoubtedly > hit the wall trying to figure out why they couldn't just switch > from memcache or dbm back to shmcb. Someone else will break there > server simply removing unfamiliar modules from the list, > particularly one which appears nowhere in the ASF HTTP Server > module documents lists. > > This, and the mod_slotmem_* objects, really make lousy modules.
Isn't the answer to this that all consumers of slotmem and socache should simply point to the mod_slotmem_*/mod_socache_* modules in the error message if the configured provider is not found? Then the user would immediately know that another module is required.
