You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by Massimo Manghi <ma...@alice.it> on 2020/05/02 22:27:16 UTC
Apache Rivet 3.2 - post pandemic release
Hi guys, I hope you're doing well and if the pandemic reached your
whereabouts I hope you got around it uneventfully. In Italy the pandemic
hit very hard, especially here in the densely populated north where a
large portion of the economic and industrial capacity of the country is
located. I live not far from Lombardy where the pandemic hit very hard.
Given the intense communication with this region we too had a relatively
large number of casualties. Things are now steadily improving, but the
world ahead of us is going to be very different....
Anyway, being stuck at home most of the time gave me the chance to work
on the 3.2 version (which is currently the master branch). I think I'll
work on it next week trying to improve the test system, but I think the
module is ready.
New features:
- Threaded bridges (such as the worker bridge) cried loud for the
possibility of having single threads terminate by calling ::rivet::exit
without affecting other threads. This feature can be enabled by setting
the SingleThreadExit configuration parameter. The prefork bridge is
unaffected
- New command ::rivet::thread_id that returns the thread
identification in a format that emulates command ::thread::id (saving
the need to load the Thread package in order to get this information).
The command returns the thread id also as a decimal number, which is the
way it is printed in the Apache error log
bug fixes
- The lazy bridge has been simplified by removing some counters and
variables used during its development for testing. Also the access to
some variables has been protected by requiring lock on a mutex.
- Rivet_Upload modified. The upload command crashed under some
circumstances (invalid argument list) due to wrong argument checking.
Functions in src/mod_rivet_ng/Tclwebapache.c called by Rivet_Upload are
now responsible to return a value to the interpreter. Even though this
required the task of handling the result to be written within each
function, my opinion is that this approach allows a more precise
handling of Tcl objects. All of these functions already use Tcl status
codes in order to communicate with the caller, Rivet_Upload now simply
returns the code they return without further processing
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Apache Rivet 3.2 - post pandemic release
Posted by Brice Hamon <no...@gmail.com>.
Hello Massimo,
Thank you a lot for your work and dedication during this terrible time
in Italie.
My thoughts are with you.
Regards,
Brice.
On Sat, May 2, 2020 at 6:27 PM Massimo Manghi <ma...@alice.it> wrote:
>
> Hi guys, I hope you're doing well and if the pandemic reached your
> whereabouts I hope you got around it uneventfully. In Italy the pandemic
> hit very hard, especially here in the densely populated north where a
> large portion of the economic and industrial capacity of the country is
> located. I live not far from Lombardy where the pandemic hit very hard.
> Given the intense communication with this region we too had a relatively
> large number of casualties. Things are now steadily improving, but the
> world ahead of us is going to be very different....
>
> Anyway, being stuck at home most of the time gave me the chance to work
> on the 3.2 version (which is currently the master branch). I think I'll
> work on it next week trying to improve the test system, but I think the
> module is ready.
>
> New features:
>
> - Threaded bridges (such as the worker bridge) cried loud for the
> possibility of having single threads terminate by calling ::rivet::exit
> without affecting other threads. This feature can be enabled by setting
> the SingleThreadExit configuration parameter. The prefork bridge is
> unaffected
>
> - New command ::rivet::thread_id that returns the thread
> identification in a format that emulates command ::thread::id (saving
> the need to load the Thread package in order to get this information).
> The command returns the thread id also as a decimal number, which is the
> way it is printed in the Apache error log
>
> bug fixes
>
> - The lazy bridge has been simplified by removing some counters and
> variables used during its development for testing. Also the access to
> some variables has been protected by requiring lock on a mutex.
>
> - Rivet_Upload modified. The upload command crashed under some
> circumstances (invalid argument list) due to wrong argument checking.
> Functions in src/mod_rivet_ng/Tclwebapache.c called by Rivet_Upload are
> now responsible to return a value to the interpreter. Even though this
> required the task of handling the result to be written within each
> function, my opinion is that this approach allows a more precise
> handling of Tcl objects. All of these functions already use Tcl status
> codes in order to communicate with the caller, Rivet_Upload now simply
> returns the code they return without further processing
>
> -- Massimo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> For additional commands, e-mail: rivet-dev-help@tcl.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Apache Rivet 3.2 - post pandemic release
Posted by Massimo Manghi <ma...@unipr.it>.
Dear Harald and Brice, thank you for your kind messages.
-- Massimo
On 5/4/20 2:24 PM, Harald Oehlmann wrote:
> Massimo,
> my compassion to Italy. The series of unpleasant events to such a
> beatiful country full of beautiful people is unbelievable.
>
> All ok here in Berlin.
>
> Harald
>
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Apache Rivet 3.2 - post pandemic release
Posted by Harald Oehlmann <ha...@elmicron.de>.
Massimo,
my compassion to Italy. The series of unpleasant events to such a
beatiful country full of beautiful people is unbelievable.
All ok here in Berlin.
Harald
Am 03.05.2020 um 00:27 schrieb Massimo Manghi:
> Hi guys, I hope you're doing well and if the pandemic reached your
> whereabouts I hope you got around it uneventfully. In Italy the pandemic
> hit very hard, especially here in the densely populated north where a
> large portion of the economic and industrial capacity of the country is
> located. I live not far from Lombardy where the pandemic hit very hard.
> Given the intense communication with this region we too had a relatively
> large number of casualties. Things are now steadily improving, but the
> world ahead of us is going to be very different....
>
> Anyway, being stuck at home most of the time gave me the chance to work
> on the 3.2 version (which is currently the master branch). I think I'll
> work on it next week trying to improve the test system, but I think the
> module is ready.
>
> New features:
>
> - Threaded bridges (such as the worker bridge) cried loud for the
> possibility of having single threads terminate by calling ::rivet::exit
> without affecting other threads. This feature can be enabled by setting
> the SingleThreadExit configuration parameter. The prefork bridge is
> unaffected
>
> - New command ::rivet::thread_id that returns the thread identification
> in a format that emulates command ::thread::id (saving the need to load
> the Thread package in order to get this information). The command
> returns the thread id also as a decimal number, which is the way it is
> printed in the Apache error log
>
> bug fixes
>
> - The lazy bridge has been simplified by removing some counters and
> variables used during its development for testing. Also the access to
> some variables has been protected by requiring lock on a mutex.
>
> - Rivet_Upload modified. The upload command crashed under some
> circumstances (invalid argument list) due to wrong argument checking.
> Functions in src/mod_rivet_ng/Tclwebapache.c called by Rivet_Upload are
> now responsible to return a value to the interpreter. Even though this
> required the task of handling the result to be written within each
> function, my opinion is that this approach allows a more precise
> handling of Tcl objects. All of these functions already use Tcl status
> codes in order to communicate with the caller, Rivet_Upload now simply
> returns the code they return without further processing
>
> -- Massimo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> For additional commands, e-mail: rivet-dev-help@tcl.apache.org
>
--
ELMICRON Dr. Harald Oehlmann GmbH
Koesener Str. 85
06618 NAUMBURG - Germany
Phone: +49 3445 781120
Direct: +49 3445 781127
www.Elmicron.de
German legal references:
Geschaeftsfuehrer: Dr. Harald Oehlmann
UST Nr. / VAT ID No.: DE206105272
HRB 212803 Stendal
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Apache Rivet 3.2 - post pandemic release
Posted by Massimo Manghi <ma...@unipr.it>.
I promised to work on the test suite. My goal was to have a test suite
that accepted two optional arguments, one for selecting a MPM module,
the second for selecting a specific bridge, but I had no time for
working on it. As soon as this goal is finished I will prepare a 3.2
release candidate.
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Apache Rivet 3.2 - post pandemic release
Posted by Brice Hamon <no...@gmail.com>.
Thanks for the update Massimo. We will be ready to test when you are.
Thank you
Brice.
On Mon, Sep 28, 2020, 12:43 AM Massimo Manghi <ma...@alice.it>
wrote:
> Hi everyone,
>
> I hope you're doing well.
>
>
> the 3.2 release is now almost ready. Sorry for the long hiatus that
> elapsed before I could actually finalize the last features I planned.
>
> mod_rivet test suite has been extended to allow testing with any MPMs
> and in combination with different MPM bridges. The only non-default
> meaningful test would be with the prefork MPM and the worker bridge.
> Selecting a MPM causes mod_rivet to load the default bridge. This new
> feature still need documentation, but I think I can write something
> about it rather soon
>
> -- Massimo
>
> On 5/3/20 12:27 AM, Massimo Manghi wrote:
> > Hi guys, I hope you're doing well and if the pandemic reached your
> > whereabouts I hope you got around it uneventfully. In Italy the pandemic
> > hit very hard, especially here in the densely populated north where a
> > large portion of the economic and industrial capacity of the country is
> > located. I live not far from Lombardy where the pandemic hit very hard.
> > Given the intense communication with this region we too had a relatively
> > large number of casualties. Things are now steadily improving, but the
> > world ahead of us is going to be very different....
> >
> > Anyway, being stuck at home most of the time gave me the chance to work
> > on the 3.2 version (which is currently the master branch). I think I'll
> > work on it next week trying to improve the test system, but I think the
> > module is ready.
> >
> > New features:
> >
> > - Threaded bridges (such as the worker bridge) cried loud for the
> > possibility of having single threads terminate by calling ::rivet::exit
> > without affecting other threads. This feature can be enabled by setting
> > the SingleThreadExit configuration parameter. The prefork bridge is
> > unaffected
> >
> > - New command ::rivet::thread_id that returns the thread
> > identification in a format that emulates command ::thread::id (saving
> > the need to load the Thread package in order to get this information).
> > The command returns the thread id also as a decimal number, which is the
> > way it is printed in the Apache error log
> >
> > bug fixes
> >
> > - The lazy bridge has been simplified by removing some counters and
> > variables used during its development for testing. Also the access to
> > some variables has been protected by requiring lock on a mutex.
> >
> > - Rivet_Upload modified. The upload command crashed under some
> > circumstances (invalid argument list) due to wrong argument checking.
> > Functions in src/mod_rivet_ng/Tclwebapache.c called by Rivet_Upload are
> > now responsible to return a value to the interpreter. Even though this
> > required the task of handling the result to be written within each
> > function, my opinion is that this approach allows a more precise
> > handling of Tcl objects. All of these functions already use Tcl status
> > codes in order to communicate with the caller, Rivet_Upload now simply
> > returns the code they return without further processing
> >
> > -- Massimo
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> > For additional commands, e-mail: rivet-dev-help@tcl.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> For additional commands, e-mail: rivet-dev-help@tcl.apache.org
>
>
Re: Apache Rivet 3.2 - post pandemic release
Posted by Massimo Manghi <ma...@alice.it>.
Hi everyone,
I hope you're doing well.
the 3.2 release is now almost ready. Sorry for the long hiatus that
elapsed before I could actually finalize the last features I planned.
mod_rivet test suite has been extended to allow testing with any MPMs
and in combination with different MPM bridges. The only non-default
meaningful test would be with the prefork MPM and the worker bridge.
Selecting a MPM causes mod_rivet to load the default bridge. This new
feature still need documentation, but I think I can write something
about it rather soon
-- Massimo
On 5/3/20 12:27 AM, Massimo Manghi wrote:
> Hi guys, I hope you're doing well and if the pandemic reached your
> whereabouts I hope you got around it uneventfully. In Italy the pandemic
> hit very hard, especially here in the densely populated north where a
> large portion of the economic and industrial capacity of the country is
> located. I live not far from Lombardy where the pandemic hit very hard.
> Given the intense communication with this region we too had a relatively
> large number of casualties. Things are now steadily improving, but the
> world ahead of us is going to be very different....
>
> Anyway, being stuck at home most of the time gave me the chance to work
> on the 3.2 version (which is currently the master branch). I think I'll
> work on it next week trying to improve the test system, but I think the
> module is ready.
>
> New features:
>
> - Threaded bridges (such as the worker bridge) cried loud for the
> possibility of having single threads terminate by calling ::rivet::exit
> without affecting other threads. This feature can be enabled by setting
> the SingleThreadExit configuration parameter. The prefork bridge is
> unaffected
>
> - New command ::rivet::thread_id that returns the thread
> identification in a format that emulates command ::thread::id (saving
> the need to load the Thread package in order to get this information).
> The command returns the thread id also as a decimal number, which is the
> way it is printed in the Apache error log
>
> bug fixes
>
> - The lazy bridge has been simplified by removing some counters and
> variables used during its development for testing. Also the access to
> some variables has been protected by requiring lock on a mutex.
>
> - Rivet_Upload modified. The upload command crashed under some
> circumstances (invalid argument list) due to wrong argument checking.
> Functions in src/mod_rivet_ng/Tclwebapache.c called by Rivet_Upload are
> now responsible to return a value to the interpreter. Even though this
> required the task of handling the result to be written within each
> function, my opinion is that this approach allows a more precise
> handling of Tcl objects. All of these functions already use Tcl status
> codes in order to communicate with the caller, Rivet_Upload now simply
> returns the code they return without further processing
>
> -- Massimo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> For additional commands, e-mail: rivet-dev-help@tcl.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org