Greg Stein <[EMAIL PROTECTED]> writes: > Personally, I view httpd-2.0 as a completely open and active repository. I > even consider API changes as somewhat acceptable. :-)
> Re: API changes. That is what we have ap_mmn.h for. However, what we've done > in the past (and I agree with), is that we balance an MMN bump against > whatever is causing the problem. We don't want to invalidate third-party > modules just to add some stupid edge case feature. +1 for *at least* the next few months, long-term pain is minimized by getting the API right as long as it doesn't require a drastic rewrite of the module as time goes on (more modules ported to 2.0, more people following 2.0 releases closely), pain to the community (including us) of changing the API goes up so the threshhold for what justifies an API change goes up too and we shouldn't forget that the APR API affects Apache module authors too, and that API is probably going to change leading up to APR 1.0 (function renames for one thing) -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
