W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2004

[VxML 2.0] Submit namelist restriction when working with ECMAScri pt objects

From: Royles, Chris <Chris.Royles@vicorp.com>
Date: Fri, 6 Feb 2004 15:27:51 -0000
Message-ID: <A10DE5600B42CB4EABF446C98C053B8E67795C@Bulldog.vicorp.co.uk>
To: www-voice@w3.org

I am looking for advice regarding the handling of composite objects returned
from subdialogs and submitted through a namelist. We are working with the
VxML 2.0 standard, we carry out a lot of interaction between subdialog
actions and remote application servers.

My question is: 
How can I take an ECMAScript object such as 'result' and pass the 'arbitrary
number' of properties it contains back through to the application server
through a submit namelist?

Details are:
Consider a scenario where I call a subdialog. The sub dialog sets up a
number of variables and returns them to the application, these variables are
then to passed back to an application server to determine what to do next.

For example

<!-- Do the sub dialog -->
<subdialog name="result" src="subdialog.vxml" namelist="input1 input2">

    <!-- Nasty ECMAScript???-->

    <!-- Inform the application server of the values returned -->
    <submit maxage="0" next="last.vxml" namelist="result" /> 


The problem is, the 'result' object is a composite of the variables listed
in the subdialogs return statement. For example


I may not know in advance the list of properties the result returns, I
really want a remote server to unpick this and carry out the evaluation of
the name/value list.
I have no straightforward mechanism of passing this information back through
the namelist of the submit.
Currently we have some nasty ECMAScript where indicated that essentially
serialises the result object into another variable and passes that variable.

Does anybody have an elegant solution to this problem? Any feedback or
comments are very welcome.

regards, Chris
Received on Friday, 6 February 2004 10:29:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:37 UTC