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 server-side ActionScript 113
The arguments in the following table can be passed only as an array of objects in the params
argument of the
CF.http() function:
You can write the
CF.http() function using either named arguments or positional arguments.
The positional argument style supports a subset of
CF.http arguments, although the named
argument style is more readable than the positional argument style.
The
CF.http() function accepts the following arguments using the named argument style:
CF.http
({
method:"get or post",
url:"URL",
username:"username",
password:"password",
resolveurl:"yes or no",
params:arrayvar,
path:"path",
file:"filename"
})
In the named argument style, braces surround the function arguments.
The positional argument approach supports a subset of
CF.http arguments, but it lets you code
in a more succinct and efficient style. The schema for the positional argument style is as follows:
CF.http(url);
CF.http(method, url);
CF.http(method, url, username, password);
CF.http(method, url, params, username, password);
Responseheader Response header. If there is one instance of a header key, you can access the
value as a simple type. If there is more than one instance, values are put in an
array in the
responseHeader structure.
Statuscode HTTP error code and associated error string, which returns the following HTTP
status codes:
400: Bad Request
401: Unauthorized
403: Forbidden
404: Not Found
405: Method Not Allowed
Argument Description
name Variable name for data that is passed
type Transaction type:
• URL
• FormField
• Cookie
• CGI
• File
value Value of URL, FormField, Cookie, File, or CGI variables that are passed
Property Description