On 12 October 2010 00:02, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Igor,
[ snip ]
> outerFinalizationLoop
[ snip ]

> (there are details like the use of handleFinalizationQueueOverflow that you
> can ignore)

> HTH
> Eliot

Okay, i got the idea.
Each finalizer (or executor) is first pushed to shared queue.
Then there is a separate process which fetching them one by one from
queue and sends #finalize.
If that process dies (due to some error), then queue starts growing
up, up to the point that outer process
(responsible for pushing finalizers to queue), starts another process
to feed from it.

Right?

-- 
Best regards,
Igor Stasenko AKA sig.