ISSUE-47: Additional MMI lifecycle events

Ingmar

Additional MMI lifecycle events

State:

CLOSED

Product:

MMI Architecture

Raised by:

Ingmar Kliche

Opened on:

2007-11-09

Description:

Additional MMI lifecycle events

1. The IM needs a lifecycle event to start a new modality component instance (e.g. to instruct the VXML server to start a new VXML modality instance)

We propose to define an event pair

newMcInstanceRequest/newMcInstanceResponse

newMcInstanceRequest:
- ImInstance-ID: Interaction manager instance ID (sender-ID)
- URI: Document URI

newMcInstanceResponse:
- ImInstance-ID: Interaction manager instance ID (receiver-ID)
- McInstance-ID: Modality component instance ID (sender-ID)
- result (success/failure)

2. The IM needs a lifecycle event to terminate a modality component instance

We propose to define an event pair

mcInstanceDestroyRequest/mcInstanceDestroyResponse

mcInstanceDestroyRequest
- ImInstance-ID: Interaction manager instance ID (sender-ID)
- McInstance-ID: Modality component instance ID (instance to be destroyed)

mcInstanceDestroyResponse
- ImInstance-ID: Interaction manager instance ID (receiver of the message)
- McInstance-ID: Modality component instance ID (instance which has been destroyed)
- result (success/failed)

3. A modality component instance may be exiting at any time (e.g. user hang up, user closed GUI browser). The modality component needs a lifecycle event to inform the IM about exiting (immediately).

This exiting could be seen as a special of finalizing execution. It may therefore make sense to use a special "Done" event. The IM may not respond to that message because the modality component will probably not be able to receive any message afterwards.

Scott/Ingmar

Related Actions Items:

No related actions

Related emails:

1. ISSUE-47 (Ingmar): Additional MMI lifecycle events (from sysbot+tracker@w3.org on 2007-11-09)

Related notes:

Display change log