|
I am confused about the documentation
in a couple of places.
First, the mk::file open command
description says you can have any number of readers OR one writer. Mark
Roseman's documentation even says only one user - period. The next
sentence indicates the -extend option can add data at the end of the database
without affecting the readers. Does this imply that you can have multiple
readers and one writer using the -extend option, or multiple writers using
-extend?
Second, using -extend says readers can
adjust to changes using rollback, which is really a roll-forward. When you
examine the mk::file rollback command, it says it cancels all pending changes
and reverts to what was last stored on the file. How would this
work?
Would a writer just do
this?
mk::file open
-extend
. .
.
mk::row
append
mk::file::commit
. .
.
Then would subsequent requests
by a reader locate the data by always doing this?
mk::file open
-extend
. .
.
mk::file rollback
mk::get
....
In other words, ALWAYS do a mk::file
rollback before any read operation?
In actual practice, I need a DB that
can be changed by multiple locations, and those other locations need to
immediately "recognize" that a change has occurred. Metakit in my tests
seems wonderful, but I can't get around the above requirement based upon my
understanding of the documentation. I have been investigating other
options, also, but none are as appealling as Metakit.
Thanks.
Ray Mosley
[EMAIL PROTECTED] |
_____________________________________________ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
