Implements interfaces:
This is the default handler for the gateway. It's job is to handle everything that is specific to Amf for the gateway.
Located in /Amfphp/Core/Amf/Handler.php (line 18)
set this if you need additional headers in the response. They will be added after normal treatment
set this if you need additional messages in the response. They will be added after normal treatment
Amf specifies that an error message must be aimed at an end point. This stores the last message's response Uri to be able to give this end point
in case of an exception during the handling of the message. The default is '/1', because a response Uri is not always available
creates a ServiceCallParamaeters object from an Amfphp_Core_Amf_Message
supported separators in the targetUri are '/' and '.'
process a request and generate a response.
throws an Exception if anything fails, so caller must encapsulate in try/catch
FILTER_AMF_EXCEPTION_HANDLER
= 'FILTER_AMF_EXCEPTION_HANDLER'
(line 44)
filter called for exception handling an Amf packet/message, to give a plugin the chance to handle it.
This is for the Flex Messaging plugin to be able to intercept the exception and say it wants to handle it
FILTER_AMF_REQUEST_HEADER_HANDLER
= 'FILTER_AMF_REQUEST_HEADER_HANDLER'
(line 27)
filter called for each amf request header, to give a plugin the chance to handle it.
Unless a plugin handles them, amf headers are ignored Headers embedded in the serialized requests are regarded to be a Amf specific, so they get their filter in Amf Handler
FILTER_AMF_REQUEST_MESSAGE_HANDLER
= 'FILTER_AMF_REQUEST_MESSAGE_HANDLER'
(line 36)
filter called for each amf request message, to give a plugin the chance to handle it.
This is for the Flex Messaging plugin to be able to intercept the message and say it wants to handle it
Documentation generated on Mon, 23 Jan 2012 17:22:06 -0300 by phpDocumentor 1.4.3