| CCXML 1.0-W3C Development Guide | Home | Frameset Home |
|
<?xml version="1.0" encoding="UTF-8"?>
<ccxml> element pair. This will contain all other CCXML elements, which essentially defines the start and end of our CCXML document.
<?xml version="1.0" encoding="UTF-8"?>
<ccxml version="1.0">
</ccxml>
<?xml version="1.0" encoding="UTF-8"?>
<ccxml version="1.0">
<var name="MyVariable" expr="'This is a CCXML Variable'"/>
</ccxml>
<?xml version="1.0" encoding="UTF-8"?>
<cxml version="1.0">
<var name="MyVariable" expr="'This is a CCXML Variable'"/>
<log expr="'*** Hello World. I just made a variable: ' + MyVariable + ' ***'"/>
</ccxml>
<log> tag is subject to the same rules regarding ECMAScript expressions as <var> because of the "expr" attribute. Don't be scared. Remember that we aren't actually outputting any audio for this tutorial, and when we call in to test the application, we will hear dead silence, followed by a hang-up: This is normal, as our method of verifying that our code works is via the logging stream.<exit> tag will terminate the session, resulting in a hangup on all lines. This tag is critical and should, if you are a highly skilled, phone-markup coder, be included in every script. Applications that do not have an <exit> point may never be terminated, resulting in a dead session. Thick-necked thugs may ring your door-bell to deliver a heavy sack beating should these dead sessions accumulate too often. Definite "termination behavior" for each CCXML session is always a good idea. It improves your document and your longevity.
<?xml version="1.0" encoding="UTF-8"?>
<ccxml version="1.0">
<var name="MyVariable" expr="'This is a CCXML Variable'"/>
<log expr="'*** Hello World. I just made a variable: ' + MyVariable + ' ***'"/>
<exit/>
</ccxml>
<exit>| ANNOTATIONS: EXISTING POSTS |
| login |
|