-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> Max Bowsher wrote: >> What is the expected level of source compatibility for authz modules >> between 2.2 and 2.3? >> >> I'm confused, as some parts of the authz framework on trunk seem to >> be attempting to allow some compatibility, whilst other parts do not. >> >> Clarification would be welcome, as I'd like to write some patches for >> the authz code, but don't want to do unnecessary work upholding >> compatibility that isn't actually intended, or produce flawed patches >> which decrease compatibility.
Brad Nicholes wrote: > It is less than going from 2.0 -> 2.2. Authn modules will need to be > recompiled but should not need to be patched. Authz modules on the > other hand will need to be converted from hook based to provider based. > You can see the work that would need to be done to an Authz module by > comparing a 2.2 authz module source with one from trunk. As far as > compatibility goes, authz functionality remains the same but the module > architecture is different. Thankyou. In light of this clarification, I have a further question: is there any reason why mod_authz_default should not be folded into mod_authz_core? Thanks, Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) iD8DBQFEGZ+tfFNSmcDyxYARAjaxAJ9M1i/OYZ5maX0tuVMFXcoDpDfiQgCfUnBf ozZzHtx9g9NhtRCXlvUTr/w= =K6LX -----END PGP SIGNATURE-----
