basically this works the same way as a "set $1" message box between two sliders, except it will cause output from both sliders rather than having one "slave" slider.
The idea behind this should not have worked theoretically : i thought "yeah a message comes in a trigger, bangs a gate to pass through it and right after that it rebangs, so the gate will be closed for the next message wich would have been a fedback otherwise." I didn't think, logically, that the next message to come would retrigger everything, and pass, setting up a loop anyway. Luckily it just works fine, not too sure why, maybe just the time of calculation needed to trigger the thing makes it impossible to have the so feared stack overflow.
I tried it with several kind of messages, the trigger objects outputs a list, so far it works fine for any kind of message. Let me know if there is trouble somewhere.
So, i guess anyone has its own methode to circumvent that kind of max limitation, but maybe will it be helpfull to some people :)