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

[Mike Kerner]

Unfortunately, there is not very much written on the topic of multi-stage
commits.  You will be able to find information on "two-phase commits",
which is a very basic version of this idea, but TPC involves state
certainty.  MSC does not.

Multi-stage commits are sort-of a cross between thinking about data in
quantum mechanics terms (i.e. the answer to any question depends on whom
you ask and when, and the likelihood that all answers will be correct, even
if they are different from each other), and two-phase commits - across many
nodes.  Yes, there are very important reasons to implement a solution this
way.  The U. S. Navy, for instance, has, in some cases 25-30 stage commits.


On Thu, Dec 5, 2013 at 10:41 PM, Robert Sneidar <slylabs13 at me.com> wrote:

> Multi-stage commits? Wow! I never knew there was such a thing! I’d like to
> talk about that! I’m going to google that one.
>
> Bob
>
>
> On Dec 3, 2013, at 9:47 AM, Mike Kerner <MikeKerner at roadrunner.com> wrote:
>
> > 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.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
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."