Communicating between to standalones with "write to process" - Found word(s) list error in the Text body
MikeKerner at roadrunner.com
Mon Dec 2 01:54:33 CET 2013
What he's suggesting is just a semaphore, which is common with DBMS's.
He's also correct that you can do it with a hidden, secondary stack being
the gatekeeper for the DB.
Another option would be to use Valentina Server or to compile your own
little application to be a database server.
On Sun, Dec 1, 2013 at 6:59 PM, Dr. Hawkins <dochawk at gmail.com> wrote:
> On Sun, Dec 1, 2013 at 3:37 PM, Bob Sneidar <bobsneidar at iotecdigital.com
> > Since you cannot open sqlite read only in LC (that might be a nice
> > feature), create a text file before opening database, checking first for
> > its existence before opening. If it exists then another stack has it
> This would be more cumbersome than what I'm trying to avoid . . .
> I get a half-second or so lag from hitting a db across town. *If* livecode
> were multithreaded, even weakly, i could use SQLite locks. My tentative
> solution is a slave process, so I pass off the updates to the remote db to
> the slave, and "eventually" the update comes back from the slave.
> If I play with the disk file, I've slowed things down even more than the
> in-memory shenanigans . . .
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> use-livecode mailing list
> use-livecode at lists.runrev.com
> 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