Unless we need to remove elements in the middle of a list, an array based variant is always faster.

There's no need for the current replica to further process the
request.

If a reply message completes a certificate while in the same
moment the lock acquire inside invoke times out then the following
retry instruction can reset the certificate even though the lock was
already released.

This ensures that the output of multiple threads won't be mixed up.

As both stdout and stderr point to the same file this can
cause garbling of log outputs between threads.

This simplifies handling of only part-time active clients

The first sequence number on the replicas is zero

Conflicting read request replies are not the leaders fault. So just
resend the request normally the first time.

A client could also reset it's certificate and retry the read
request for a newer sequence number.

This should lead to less mangled stack traces