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

Re: allowing <onentry> and <onexit> inside <final>

From: Torbjörn Lager <torbjorn.lager@gmail.com>
Date: Thu, 5 Apr 2007 22:30:35 +0200
Message-ID: <6ad4bdae0704051330n5e6d3c31i68b307b93362ada0@mail.gmail.com>
To: "Barnett, James" <James.Barnett@aspect.com>
Cc: www-voice@w3.org, "Serge Voloshenyuk" <serge_voloshenyuk@yahoo.com>

I think that this is a good idea. But what about the <onexit> children
of a <final> which is a child of <scxml>? Will they ever be run? Is
the concept of 'exiting' applicable to this state?

Regards,
Torbjörn


On 4/5/07, Barnett, James <James.Barnett@aspect.com> wrote:
>
>
>
>
> We have provisionally decided to accept the following change request for
> inclusion in the next draft of the spec.  The <final> element will be
> allowed to have <onentry> and <onexit> children:
>
>   From Serge Voloshenyuk:
>
> Hi
> It could be useful to have <onentry> and <onexit> in <final> state.
> <onentry>: for send results
> <onexit>: for data cleanups.
>
> Regards, Serge.
>
>
>
Received on Thursday, 5 April 2007 20:41:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 April 2007 20:41:30 GMT