Hello, Massimo ! > Having just apache-2 to take care of would give much more > freedom to the development and simplify the tests. > > David, you're the policy maker here, what do you think? > Maybe 1_0 is stable enough to be the final release for > apache1.x? > > -- Massimo I disagree. I think we should support apache-1.3.x version, as long as it will be used. And it will be used, because apache-1.3.x is the only version of apache that has been properly audited for security holes, and spent enough time in world wide production to be considered sort of reliable. I have nothing against neither apache2, nor by against folks who are using or developing it but here is my short list of contras: -- first and most important - apache2 is a bad known by its api changes which break backward compatibility with in apache2 itself, just recall apache 2.0 - apache 2.2 switch. -- second introduction of this threading stuff - very questionable from my point of view, of course there are some benefits on platforms with expensive process creation, but on unix - it just makes things much more complicated, threading support varies between different common unixes greatly. What i am thinking about is to make rivet so called "apr-centric" not "apache-centric" - most of action code should be redone using apr and tcl functions and made apache independent, leaving apache dependent bits as thin as it will be possible. IMHO 2.0-2.2 apache API breakage was not the last one :) I dont want to be dependant on it in the future.
Regards Valery. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
