Hi Valery,
As usual your opinions exhibit strong points.
I accept your point of view if Rivet must have new and
absolutely necessary features that are missing now and for which
we don't have any other option except for bringing them into
a future architecture. I mean feature for the application level
For this development we may add new features for the apache1.x
module developing in pure Tcl or use the strategy of encapsulating
them into packages (like in the package Rivet that maybe should be
renamed as Rivetlib) At that level adding more feature to the 1_0
should be easy.
Valery Masiutsin wrote:
Hello, 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.
this is sad, but we have to put up with it.
-- 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.
this looks like the focal point of every future development. Threads were
on the heap years ago and now everybody seem to have fallen out with them.
Even though I still like the concept I won't make any advocacy, lest a war
of religion would break out ;-)
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.
seriously this can happen again? Maybe Rivet made the right thing:
pausing the development and waiting for Apache3.0 :-)
ciao
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
