Communicating between to standalones with "write to process" - Found word(s) list error in the Text body

Mike Kerner MikeKerner at
Tue Dec 3 12:47:16 EST 2013

OK, let's see:
As far as the vocabulary, no, sorry, that's from [a number greater than
what I'm going to admit] years of working in the DB space on lots of
platforms and on lots of very interesting problems.

The reason for using the server is that it takes most of the work out for
you, and you just worry about talking to it.  Transactions, triggers,
semaphores, record locking, etc. can all be handled that way.  Now once you
get into multi-stage commits, you and I have to talk because that's a topic
that is generally beyond the scope here.

You could, if your data set was not abhorently large, also use LC's fields
as your database, and go old school with creating a card for each record,
etc.  Then if you communicate with the stack, you're really just
communicating with a "crude" database server.

On Tue, Dec 3, 2013 at 3:40 AM, Dr. Hawkins <dochawk at> wrote:

> On Sun, Dec 1, 2013 at 4:54 PM, Mike Kerner <MikeKerner at
> >wrote:
> > What he's suggesting is just a semaphore, which is common with DBMS's.
> >
> Ahh, vocabulary that I need :)
> Do you have any suggestions for me to read on that.
> [During my dissertation work, which created a third branch of dynamic
> programming, I was well into it when I realized that I'd recreated either
> lossy virtual memory or disk caching . . . {the search space was too large
> to keep an index of tried values, so it kept more recent ones and
> recalculated}]
> > He's also correct that you can do it with a hidden, secondary stack being
> > the gatekeeper for the DB.
> >
> > *whew*
> :)
> > Another option would be to use Valentina Server or to compile your own
> > little application to be a database server.
> >
> But would there be any value in using a database server rather than just a
> clone of the stack?  That clone can use the same codebase, and
> automatically be updated by definition . . .
> Thanks
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."

More information about the Use-livecode mailing list