Guido Casper <[EMAIL PROTECTED]> writes: > > Hunsberger, Peter wrote: > >>You can call it whatever you want but a "state" in a FSM and a > >>"continuation" in a script are exactly the same thing, they need to > >>contain the same amount of data to be able to resort the execution. > >> > >>The problems in replicating one across containers will be the same > >>problems in replicating the other. > > > > > > Hmm, I don't think so. A FSM (in general) and a continued > script are > > in not isomorphically equivalent in CS terms, so there can be no > > equivalence between the maintenance of state and the > maintenance of a > > continuation. However, for practical purposes, I would agree, they > > need to contain more or less the same information. > > While this would be true if you are just talking about the > continuation > ID (while destroying the whole idea of querying the repo for > task lists) > you actually have to maintain the whole continuation stack.
I think the point was that the "extended state path list" and the continuation stack would work out to the same thing. But maybe I'm missing something...
