A session represents all the components (ASR, TTS, NLU, etc.) necessary to carry on a conversation with Diatheke. A single session keeps track of a dialog’s current state, with all possible states being defined by a Diatheke model. The session transitions between states based on user input, which can be either text or audio. In response to user input, the Diatheke server will notify the client of events that occur as part of the transition, including TTS generated audio and requests to execute commands.
The following sections describe how to use use a session in the SDK.