User Guide
Table Of Contents
- Contents
- About Flash Remoting
- Getting Started
- Using Flash Remoting ActionScript
- Using the RemotingConnector component (Flash Professional only)
- Using Flash Remoting Data in ActionScript
- About Flash Remoting and data types
- Understanding Action Message Format
- Converting from ActionScript to application server data types
- Converting from application server data types to ActionScript
- ColdFusion to ActionScript data conversion issues
- About working with objects
- About working with RecordSet objects
- About working with XML
- The NetConnection Debugger
- Using Flash Remoting with ColdFusion MX
- Using Flash Remoting for Java
- About Flash Remoting for Java
- Calling Java classes or JavaBeans from ActionScript
- Calling Enterprise JavaBeans (EJBs) from Flash
- Calling servlets and JSPs from Flash
- Calling JMX MBeans from Flash (JRun only)
- Calling server-side ActionScript from Flash (JRun only)
- Handling function results in ActionScript
- Using Flash Remoting with JRun security
- Passing XML objects between Flash and Java
- Viewing Flash Remoting log entries
- Using Flash Remoting for Microsoft .NET
- Flash Remoting for Microsoft .NET
- Calling ASP.NET pages from Flash
- Making an ASP.NET page available to Flash Remoting
- Getting a reference to an ASPX-based service in ActionScript
- Invoking ASPX pages in ActionScript
- Using the Flash Remoting custom server control in ASPX pages
- Using the Flash Remoting namespace in code-behind files
- Using ASP.NET state management with Flash Remoting
- Using ASP.NET exception handling
- Using ADO.NET objects with Flash Remoting
- Displaying a RecordSet object in Flash with ActionScript
- Calling web services from Flash
- Calling ASP.NET assemblies from Flash
- Viewing Flash Remoting log entries
- Using NetServices and Connection Classes
- Index

168 Appendix A: Using NetServices and Connection Classes
// initialization code specifies gateway, creates connection, calls service
if (inited == null)
{
inited = true;
NetServices.setDefaultGatewayUrl("http://localhost:8300/flashservices/
gateway")
var gatewayConnection:Connection = NetServices.createGatewayConnection();
// specify this object (this) as the responder object
howdyService =
gatewayConnection.getService("remoteservices", this);
}
// function specific result handlers
function helloWorld_Result(result)
{
// display successful result
messageDisplay.text = result;
}
function whatsUp_Result(result)
{
// display successful result
resultDisplay.text = result;
}
// default result handler
function onResult(result)
{
trace("result from onResult is: " + result);
}
// call helloWorld service function
howdyService.helloWorld();
// call other service functions
howdyService.whatsUp();
howdyService.howsItGoin();// uses default result handler
Directing results for a service to specific responder objects
You can also specify a responder object to handle the results of a specific service function. To do
this, specify the responder in the first argument of the service call. For example, the following call
to the
whatsUp() service method specifies whatsUp_Result() as the responder.
howdyService.whatsUp(new whatsUp_Result());
Note: The underlying ActionScript code removes the first parameter before invoking the service
function.
Flash Remoting directs the results to the onResult function of the specified result handler.
In the following example the service function calls specify responder objects. There are three
responder objects:
helloWorld_Result() for the helloWorld() function, whatsUp_Result()
for the
whatsUp(), and general_Result() for other service functions. Each responder object
has one result handling function,
onResult(), to handle the result returned by the service.
import mx.remoting.NetServices;
import mx.remoting.Connection;