An AMF Message contains information about the actual individual
transaction that is to be performed. It specifies the remote operation that is to be performed; a local (client) operation to be invoked upon success; and, the data to be used in the operation. <p/> This Message structure defines how a local client would invoke a method/operation on a remote server. Additionally, the response from the Server is structured identically.
Located in /Amf/Value/MessageBody.php (line 39)
Contains the actual data associated with the operation. It contains the client's parameter data that is passed to the server's operation/method.
When serializing a root level data type or a parameter list array, no name field is included. That is, the data is anonomously represented as "Type Marker"/"Value" pairs. When serializing member data, the data is represented as a series of "Name"/"Type"/"Value" combinations.
For server generated responses, it may contain any ActionScript data/objects that the server was expected to provide.
Universal Resource Identifier that uniquely targets the originator's
Object that should receive the server's response. The server will use this path specification to target the "OnResult()" or "onStatus()" handlers within the client. For Flash, it specifies an ActionScript Object path only. The NetResponse object pointed to by the Response Uri contains the connection state information. Passing/specifying this provides a convenient mechanism for the client/server to share access to an object that is managing the state of the shared connection.
Since the server will use this field in the event of an error, this field is required even if a successful server request would not be expected to return a value to the client.
A string describing which operation, function, or method is to be remotley invoked.
Constructor
Retrieve response data
Get target Uri
Retrieve target Uri
Set reply method
Set response Uri
Set target Uri
Documentation generated on Mon, 21 Jun 2010 15:33:54 -0400 by phpDocumentor 1.4.3