Ruediger Pluem wrote: > > Hm, what backport are you thinking of? I thought of backporting it to 2.2.x > not to 2.0.x. I see no general backwards compatibilty of modules written for > 2.2.x to 2.0.x.
Well, we are talking about breaking <= 2.2.3 / > 2.2.3 right? You are right, the new function would require an MMN bump. I'm rethinking this, most modules don't directly query this information, so I suppose it's not as horrible as I thought. It will be up to the module authors to be as conservative or optimistic about using this API and spelling out the version required for their module. Nevermind, no problem with backporting to 2.2 ;-) Just don't change the ap_get_server_version export or function signature, and those who want to adopt _banner will. (The more I think about this from the principle of least (unpleasant) surprise, the more I think the existing function's behavior shouldn't change, and the -new- function should provide the full description no matter what the settings for the server signature are.)
