I'm really not that much help with CF but here's an example in PHP:
This would be a language translator:
<?php
require_once 'SOAP/Client.php';
$soapclient = new SOAP_Client("WSDL/BabelFishService.wsdl","wsdl");
$result = $soapclient->call("BabelFish",array("translationmode"=>$Mode, "sourcedata" => $InputText));
print "&OutputText=$result&Go=Yes";
?>
// Mode and Input text is sent from Flash - Output text is sent back.
(Flash would just have an Input text box for what you want to translate - and a dynamic text box for what is returned) (
http://www.flash-db.net/Soap/Translate.html)
- This makes it about 10 times easier and faster then dealing with Flash.
------------------------------
The google one is about the same but slightly more complex.
I always do all the parsing on the server side to make it faster and easier to work with, try to avoid the XML part of all this as much as possible - makes it harder to format all the results (in my experience).
For Google here's how I parse all the returned Data:
for($t=0;$t<$numR;$t++) {
print "<font COLOR=\"#0066cc\" SIZE=\"+14\"><u><a href=\"$Element[URL]\" target=\"_blank\">$Element[title]</a></u></font><br>-$Element[snippet]<br><font COLOR=\"#999999\">Description: </font> <i>$Element[summary]</i><br><font COLOR=\"#008000\">$Element[URL]</font> - <b>$Element[cachedSize]</b><br><br>";
}
--------------------------
Their's a bit that's missing to that - but what it basically does is grabs the Soap Response and Loops through each returned element - Printing out the results in a format that's easy to change around. The response is then returned to Flash.
In the case of Flooge - The actual Flash is basically just 2 dynamic text area's and nothing else. 1 for search term and 1 to hold the response.
Personally I hate formatting XML with Flash's XML parser so I tend to do things this way.
Author
