ISSUE-33: Response to \"Start\" event from a component that\'s already started
Response to \"Start\" event from a component that\'s already started
- State:
- CLOSED
- Product:
- MMI Architecture
- Raised by:
- Deborah Dahl
- Opened on:
- 2007-02-19
- Description:
- If a modality component which has already started receives a new Start event
before it\'s finished, what should be the appropriate behavior? There are at
least 3 possibilities:
1. send back an error (presumably something like \"status = failure\", \"errorinfo
= \'already started\'\" in the StartResponse)
2. restart (with either new content or restart previous content if there\'s no
new content, send back \"status = success\" in StartResponse)
3. ignore (that is, send back a StartResponse with \"status = \'success\'\", and
continue doing whatever it was doing before the new Start event). - Related Actions Items:
- No related actions
- Related emails:
- [all] MMI agendas August 16-September 20, 2010 (from dahl@conversational-technologies.com on 2010-08-12)
- ISSUE-102 (EMO-33): Custom range of values for rating-scale type range? [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
- Re: [emo] Issues in EmotionML (from ashimura@w3.org on 2009-10-31)
- [emo] Issues in EmotionML (from schroed@dfki.de on 2009-10-30)
- ISSUE-33: Response to \\\'Start\\\' event from a component that\\\'s already started [MMI Architecture] (from dean+cgi@w3.org on 2007-02-19)
Related notes:
the fourth option is not to specify what happens, it's just platform-specific.
Deborah Dahl, 4 Mar 2008, 17:04:41the fourth option is not to specify what happens, it's just platform-specific.
Deborah Dahl, 4 Mar 2008, 17:05:00(from f2f) We agree on option 2. Send back the regular startResponse message. It should implicitly stop the previous running action.
Deborah Dahl, 4 Mar 2008, 17:17:32(from f2f) We agree on option 2. Send back the regular startResponse message. It should implicitly stop the previous running action.
Deborah Dahl, 4 Mar 2008, 17:17:36Display change log
