Ann,

> Firebird maintains an internal list of queued requests for locks
> inside the lock table, but nowhere else.

Is that something I could make use of? That is to say can I have
several clients requesting a lock on a specific record (waiting for
success) and the server manages serialization of these?

If it worked like Oracle's "SELECT ... FOR UPDATE", waiting for the
lock to succeed, then it would be perfect.

> You might set up a protocol
> in your application that uses a mutex (or non-interruptible compare
> and swap) to synchronize requests for your "table generator".

I am not sure I understand. How can a client mutex synchronize
requests of different clients on the server?

--Heiko