Subject Re: [Firebird-Architect] Re: Vulcan architecture and lock tables
Author Ann W. Harrison
= m. Th = wrote:

> 1. What was/is the design rationale to have one file / provider since,
> CIIW, the locks are database based?

The lock table was based on the VMS distributed lock manager. Among
the objects that are locked are databases - which makes a per database
lock table less attractive. The VMS distributed lock manager is one
of the models for the open source DLM.

> 2. Why do you use a file and not a memory space?

As it happens, the lock table is in memory.


Regards,


Ann