Definitive VoiceXML™

2.10. Organizing code into VoiceXML applications

So far, we have authored VoiceXML documents that exercise a wide range of the language features. As the size and complexity of a voice application grows, it becomes impractical to store it entirely within a single document. We have already seen examples of this where one dialog references another with a <goto next="anotherdocument.xml"/> or <link next="destination.xml"/>.

The problem that arises here is that HTTP, the protocol by which a VoiceXML interpreter communicates with the server storing the VoiceXML documents, does not maintain state. Therefore any state information that may have been created during the interpreting of one VoiceXML document is lost as soon as the next document is loaded. ...