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

Using Flash Remoting with ColdFusion pages 99
The Flash scope has several predefined variables that you can use to pass information, as described
in the following table:
When you call a ColdFusion page from a Flash application, the Flash Remoting gateway converts
ActionScript data types to ColdFusion data types. The data type of any results returned from
ColdFusion to the Flash application are converted to ActionScript data types. For more
information on this conversion, see Chapter 4, “Using Flash Remoting Data in ActionScript,” on
page 63.
Using Flash.Params to access parameters in a ColdFusion page
The
Flash.Params array contains one element for each parameter passed from ActionScript, in
the order that the parameters were passed to the ColdFusion page. You use standard ColdFusion
array syntax to reference the parameters.
For example, the following ActionScript call passes three parameters:
myService.myMethod(param1, param2, param3);
In your ColdFusion page, you access these parameters using Flash.Params, as follows:
<cfset p1=Flash.Params[1]>
<cfset p2=Flash.Params[2]>
<cfset p3=Flash.Params[3]>
The following ActionScript code calls a ColdFusion page to execute a query. The ActionScript
passes a single parameter to the ColdFusion page:
myService = new Service(
"http://localhost/flashservices/gateway",
null,
"doc_code",
null,
null);
var pc:PendingCall = myService.query1param("RipperStik");
Variable Description For more information
Flash.Params
Array containing the parameters passed from the
Flash application to the ColdFusion page. If you do
not pass any parameters,
Flash.Params still exists,
but it is empty.
See “Using Flash.Params to
access parameters in a
ColdFusion page”
on page 99.
Flash.Result
Result returned to the Flash application from the
ColdFusion page.
Note: Because ActionScript performs automatic
type conversion, do not return a Boolean literal to
Flash from ColdFusion. Return
1 to indicate true,
and return
0 to indicate false.
See “Returning results to
ActionScript” on page 102.
Flash.Pagesize
Number of records in each increment of a record
set returned to Flash from a ColdFusion page.
See “Returning record sets to
Flash” on page 103.