Flex Remoting and Messaging (2010)
4 likes3,575 views
This document discusses using Action Message Format (AMF) for integrating Flex applications via remoting and messaging. It provides an overview of AMF capabilities including remoting services that allow invoking Java methods and messaging services for real-time data push. Benefits of AMF are explained such as faster binary transfer and direct object parsing. Server-side AMF options and terminology are covered along with how to configure AMF in Flex applications using code, MXML, or configuration files. Simple examples of remoting and messaging are also presented.
Flex Remoting and Messaging (2010)
- 1. Integrating Flex using AMFRemoting & Messaging in FlexChristopher Grant - crgrant@gmail.com 1/20/2010
- 2. AgendaWhat is AMFData Integration Options in FlexCapabilities of AMFWhy it is usefulBenefits of AMFWhere to get itServer Side Options for AMFHow to use itTerminologyConfigurationExamplesSimple RemotingSimple MessagingCustom Objects
- 3. What is it
- 4. Data Integration OptionsHyper Text Transfer Protocol – HTTPHTTPServiceSimple Object Access Protocol – SOAPWebServiceAction Message Format – AMFRemotingRemoteObjectMessagingConsumerPublisher
- 5. AMF CapabilitiesRemoting Services allow your Flex application to directly invoke methods of Java objects deployed in your application server.Message Services provide a publish/subscribe infrastructure that enables your Flex application to publish messages and subscribe to a messaging destination, enabling the development of real-time data push and collaborative applications.
- 6. Why use it
- 7. Benefits of AMFBinary transfer is faster than textObjects are very small and are compressed using zlibFast Serialization/ DeserializationDesigned to serialize and deserialize quickly under low memory and slower CPU conditionsAMF data is parsed directly into objects, meaning there is no lag for interpretation or parsingActionScript Object formatSupport for Native Types and Custom classes
- 8. Where to get it
- 9. ServerSide AMF OptionsPHP: Zend, AMFPHP, WebOrb for PHP, SabreAMFJava: BlazeDS*, Red5, GraniteDS*, WebOrb for Java.Net: FluorineFx*, WebOrb* for .Net, AMF.NETPython:PyAMFRuby on Rails: RubyAMF, WebOrb for Ruby on RailsColdFusion: Built in** indicates push / messaging capabilities
- 10. How do you use it
- 11. TerminologyChannelProtocol-based conduitsChannel SetsImproves the quality of service in the face of network failures or individual Channel problemsEndpointThe server interface responsible for encoding and decoding data into messagesDestinationClient side reference to resources used for both publish-subscribe and point-to-point messagingPolling vs StreamingPolling opens & closes the connection by messageStreaming keeps the connection open at all times
- 12. Channels, Set and Endpoints Oh MY!ClientDestinationEndPointChannelStreamingDestinationDestinationEndPointChannelStreamingChannel SetDestinationEndPointChannelPollingDestination
- 13. ConfigurationCode basedAS and MXMLConfig Filesservices-configToolKitSwiz
- 14. Config FilesServices-configNeed to tell flex where it isSetup with IDE WizardSetup ManuallyFlex Compiler arguments: -services "C:\....”Pointers to remoting-config.xmlproxy-config.xmlmessaging-config.xmlUsed by Client and Server
- 15. Config File ExcerptServices-config.xml…<service-include file-path="remoting-config.xml" />…<channel-definition id="channel-amf“ class="mx.messaging.channels.AMFChannel"><endpointurl="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint" /></channel-definition>Remoting-config.xml<service id="remoting-service“ class="flex.messaging.services.RemotingService“>…<destination id="HelloWorld"><properties> <source>com.grant.Thing</source> </properties><channels> <channel ref="channel-amf" /> </channels>…</destination>…</service>
- 16. Simple MXML Excerpt<mx:RemoteObject id=“myRemoteObject" destination="HelloWorld" result="resultHandler(event)" fault="faultHandler(event)" /><mx:Buttonlabel=“SayHello“ click=" myRemoteObject.getOperation(“SayHello”).send();" />private function resultHandler(evt:ResultEvent):void{resultTxt.text= evt.result.toString();}
- 17. Real ExamplesLet’s look at code already…geez!