W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2007

RE: [SCXML] <anchor> stuff?

From: Barnett, James <James.Barnett@aspect.com>
Date: Fri, 20 Apr 2007 10:12:47 -0400
Message-ID: <57686697B4E28949A90094A6469165C701E0EAC8@ASP1EXCH1.aspect.com>
To: "Serge Voloshenyuk" <serge_voloshenyuk@yahoo.com>, <www-voice@w3.org>
Yes, all types of anchors must be popped.  The purpose of anchors is to
try to roll back the application to a previous state (hence the
snapshots of the data model.)  The purpose of the multiple anchor types
is to give the application author a choice of where to roll back to or
how much of the data model to roll back.  Normally the different anchor
types would be placed in different states or would specify different
parts of the data model to roll back.  

 

- Jim

 

________________________________

From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On
Behalf Of Serge Voloshenyuk
Sent: Thursday, April 19, 2007 6:47 PM
To: www-voice@w3.org
Subject: RE: [SCXML] <anchor> stuff?

 

Jim,

thanks for answer.



>As you say in Question 2, the most sensible way to implement anchors is

>to keep a stack of states and snapshots and then pop items off until
you

>find a match.  (Note, though that in the case where there is no match,

>you may end up not popping any items off the stack.)  



1.So, all types of anchors must be popped.

Not only the type of current anchor transition.



2.Or you mean that there is a stack for every anchor type.



If first is correct, what purpose of different types of anchors?

I thought that it's for partitioning of different parallel subtasks.

I mean no parallel substates, but different subtargets of machine
destination.



Regards, Serge







  

________________________________

Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
<http://us.rd.yahoo.com/evt=48245/*http:/autos.yahoo.com/new_cars.html;_
ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-
>  
Received on Friday, 20 April 2007 14:13:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 April 2007 14:13:17 GMT