RE: why not post mod_gzip 2.0? (was: Re: [PATCH] Add mod_gz to httpd-2.0)
The absolute best way to stay on top of API changes is to make your code available to the people making those changes. Rasmus... We don't want any distractions to the core code until it's stable. It took 5-6 months to get mod_gzip stable for 1.3.x. I doubt it will take that long in Apache 2.x but until it's stable why release something which will could cause a problem. Kevin and I have asked that mod_gzip be included in Apache 1.3.x because it's stable, been tested by thousands of users and is part of the spec. We'd like to repeat the same performance for 2.x Peter -Original Message- From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 12:08 AM To: [EMAIL PROTECTED] Subject: RE: why not post mod_gzip 2.0? (was: Re: [PATCH] Add mod_gz to httpd-2.0) Why won't you post mod_gzip 2.0 *today*? Because Apache 2.x is not STABLE, not In BETA and the API set is not yet FROZEN... When it is, we will release mod_gzip as a third party module, which we will support and maintain. I have stayed far away from this thread, but this just doesn't make any sense to me. The absolute best way to stay on top of API changes is to make your code available to the people making those changes. As soon as we had an Apache2 PHP filter it was on our public CVS server and both Doug and Ryan have tweaked it every now and then and many people have tested it and found problems. I don't understand how this could possibly be a bad thing and definitely reduces the amount of tail-chasing we will have to do later on. -Rasmus
re: why not post mod_gzip 2.0? (was: Re: [PATCH] Add mod_gz to httpd-2.0)
You and Kevin never answered my simple question: Why won't you post mod_gzip 2.0 *today*? Kevin, the best way to have mod_gzip in Apache 2.0 is to make it available. You knows i'm using it on Apache 1.3 for many times and be more than happy to see such an excellent works on 2.0 :)
RE: why not post mod_gzip 2.0? (was: Re: [PATCH] Add mod_gz to httpd-2.0)
Why won't you post mod_gzip 2.0 *today*? Because Apache 2.x is not STABLE, not In BETA and the API set is not yet FROZEN... When it is, we will release mod_gzip as a third party module, which we will support and maintain. In the meantime use mod_gz. Peter -Original Message- From: Greg Stein [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 10:34 PM To: [EMAIL PROTECTED] Subject: why not post mod_gzip 2.0? (was: Re: [PATCH] Add mod_gz to httpd-2.0) On Wed, Sep 05, 2001 at 01:46:55PM -0600, Peter J. Cranstone wrote: I suppose the only thing we can do is contribute. Kevin has, mod_gzip was released under an ASF license which was approved by the ASF Board. If there is a hidden agenda there then you're better than I at spotting it. Mod_gzip is available for 1.3.x It will be available for 2.x when you hit beta. ... Now tell me where the hidden agenda is. You and Kevin never answered my simple question: Why won't you post mod_gzip 2.0 *today*? I asked several times, but it never got answered. I seem to recall somebody stating it was being held, pending stability of the internal Apache APIs. But that isn't an issue if it is to be incorporated into Apache. Another response was look at 1.3 and port it forwards to 2.0. Why should that happen, when you've done the work? If you intend to contribute it, then why the delay, making us repeat your work? Without that simple question answered, then yes: I would think there is some kind of hidden agenda. Avoiding that question, and not posting mod_gzip 2.0 makes it appear that you are trying to hide something. The more conspiratorial-minded of us would simply believe this whole thread is to create a division and weaken the voting for mod_gz. Much like politicians will introduce a second, similar bill to confuse and divide supporters and then crush both bills. But of course that wouldn't happen here, now would it? :-) Cheers, -g -- Greg Stein, http://www.lyra.org/
