At 07:32 PM 11/16/2003, Martin Kraemer wrote: >...only that tomorrow's apr might not be 100% compatible with today's. >Think of mod_ssl's and mod_dav's problem (the apache_1.3 version). They >must always add the apache_1.3 version number to their own version number >to describe the API they require. I would not like a > apache-1.3.30-mod_ssl-2.8-20-apr-1.0.14 kind of delivery scheme.
Of course not. mod_ssl's legacy goes to apache's legacy of breaking compatibility early and often when it made things better/easier/simpler. Apache 2.0 and APR 0.9 (soon 1.0) have avoided that approach as best as possible (the poll API being the big exception.) If you need apache 2.0 you need apr 0.9. The API should be stable. If you need apache 2.2 you will need apr 1.0 (or 1.1 if changes happen to make 2.2 a possibility). And within a given point release, apache 2.2 or apr 1.1, nothing will be broken. That's the contract we are aiming for to avoid the very headache you describe above. Bill
