FLEX_TYPE_COMMAND_MESSAGE
FLEX_TYPE_COMMAND_MESSAGE
Support for flex messaging.
This plugin can be deactivated if the project doesn't need flex messaging, usually a RemoteObject in Flex.
Flex doesn't use the basic packet system. When using a remote objct, first a CommandMessage is sent, expecting an AcknowledgeMessage in return. Then a RemotingMessage is sent, expecting an AcknowledgeMessage in return. This plugin adds support for this message flow.
In case of an error, an ErrorMessage is expected
filterAmfRequestMessageHandler(Object $handler, \Amfphp_Core_Amf_Message $requestMessage) : array
filter amf request message handler
Object | $handler | null at call. If the plugin takes over the handling of the request message, it must set this to a proper handler for the message, probably itself. |
\Amfphp_Core_Amf_Message | $requestMessage | the request message |
handleRequestMessage(\Amfphp_Core_Amf_Message $requestMessage, \Amfphp_Core_Common_ServiceRouter $serviceRouter) : \Amfphp_Core_Amf_Message
handle the request message instead of letting the Amf Handler do it.
\Amfphp_Core_Amf_Message | $requestMessage | |
\Amfphp_Core_Common_ServiceRouter | $serviceRouter |
generateErrorResponse(\Exception $exception) : \Amfphp_Core_Amf_Packet
flex expects error messages formatted in a special way, using the ErrorMessage object.
\Exception | $exception |