AMF Remoting support.
A Remoting request from the client consists of a short preamble,
headers, and bodies. The preamble contains basic information about the
nature of the request. Headers can be used to request debugging
information, send authentication info, tag transactions, etc. Bodies
contain actual Remoting requests and responses. A single Remoting
envelope can contain several requests; Remoting supports batching out of
the box.
Client headers and bodies need not be responded to in a one-to-one
manner. That is, a body or header may not require a response. Debug
information is requested by a header but sent back as a body object. The
response index is essential for the Adobe Flash Player to understand the
response therefore.
tuple
|
|
|
|
tuple
|
|
|
|
|
|
|
|
|
|
Envelope
|
decode(stream,
context=None,
strict=False,
logger=None,
timezone_offset=None)
Decodes the incoming stream as a remoting message. |
source code
|
|
StringIO
|
encode(msg,
context=None,
strict=False,
logger=None,
timezone_offset=None)
Encodes AMF stream and returns file object. |
source code
|
|
|
|
|
STATUS_OK = 0
Succesful call.
|
|
STATUS_ERROR = 1
Reserved for runtime errors.
|
|
STATUS_DEBUG = 2
Debug information.
|
|
STATUS_CODES = { 0: ' /onResult ' , 1: ' /onStatus ' , 2: ' /onDebugEv ...
List of available status response codes.
|
|
CONTENT_TYPE = ' application/x-amf '
AMF mimetype.
|
|
ERROR_CODES = { 0: ' Server.Call.Failed ' }
|
|
APPEND_TO_GATEWAY_URL = ' AppendToGatewayUrl '
|
|
REPLACE_GATEWAY_URL = ' ReplaceGatewayUrl '
|
|
REQUEST_PERSISTENT_HEADER = ' RequestPersistentHeader '
|
|
ERROR_CALL_FAILED = 0
|