Jim Starkey wrote:

> ...
>
>merge classic and superserver into a single unified engine. ... two states:
>
> 1. The database file is to be opened shared. In this case locks are
> expressed in the lock manager with blocking ASTs as per classic.
> In fact, it is classic.
> 2. The database file is to be opened exclusively but multiple
> attachments are supported. Locks are not exported. This
> corresponds to superserver.
>

And the other problem for classic, synchronizing state and metadata
changes, can be done through the normal lock manager for classic and
through the lightweight lock manager for the shared server.

Regards,


Ann