Rivet next release

[Massimo Manghi <ma...@unipr.it>]

The code currently in trunk addressed the issue related with
commands being unconditionally executed also outside of a request
processing. For reason linked to the way internally APR manages memory
deallocation the request_rec object pointer stored in the module global
status could still point to valid memory, even though beyond the limit
of request processing this memory should be considered as invalid.

Commands now fail when called outside of their context and this could
break code that mistakenly called for example ::rivet::env in exit
scripts as described in bug 56290 [1]

I propose to label next release as 2.2.0 to mark the difference and
incompatibility with 2.1.4 which still rather dangerously still allows
this calls in exit scripts. In init scripts calling for instance
"::rivet::env HTTP_HOST" crashes the server also on Rivet 2.1.2 as no
request record has been processed yet and thus no surviving spurious
request_rec exists.

I rather favor to re-release in short time a 1.2.0 to secure this issue
and deprecate 1.2.4

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=56290

-- 
-- Massimo Manghi

Dipartimento di Neuroscienze
Unità di Biofisica e Fisica Medica
via Volturno 39
43125 Parma

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org