+

Search Tips   |   Advanced Search

  • Previous Topic
  • Next Topic
  • Book Index
  • Adobe Flex/AMF requests

    In This Section

  • Overview
  • AMF streaming
  • Record SSL-secure Adobe Flex/AMF requests
  • Record requests with an Adobe AIR application
  • Post-recording wizard
  • Identifiers handled by NeoLoad
  • User Interface
  • See Also

  • Requests
  • HTTP requests
  • SOAP requests
  • WebSocket requests
  • Oracle Forms requests
  • Adobe RTMP requests
  • Data Format Extension requests
  • Google Web Toolkit requests
  • Hessian requests
  • Java serialization requests
  • Siebel requests
  • Silverlight requests
  • Media requests
  • Polling requests
  • Streaming requests
  • Push messages
  • Validation
  • Global validation
  • Variable extractors
  • Advanced parameters
  • Variable correlation
  • Shortcuts
  • Compare requests and responses

  • Overview

    AMF is a binary, client-server data transfer protocol used by certain Adobe Flash applications. The optional AMF (Action Message Format) module allows load testing Adobe Flash applications developed using Adobe Flex technology, and using the AMF application protocol.

    There are several variants of the AMF binary protocol:

    For more information, click the image below to see the Neotys video about Adobe Flex in NeoLoad:

    demopage_flex


    Dependent libraries

    When recording AMF3 requests, depending on the server-side implementation, the Java classes of the objects exchanged have to be declared in NeoLoad. See Adobe Flex/AMF.


    Recording

    The following diagram shows how the Adobe Flex/AMF module functions during the recording:

    The binary data exchanged between the client and server transit through the recording proxy. It is during this transit that the Adobe Flex/AMF module analyzes and decodes the requests. Once they have been translated into XML, the requests are inserted in the project.


    Execution

    The following diagram shows how the Adobe Flex/AMF module functions when a test is run:

    The variables in the XML request are calculated and the module engine translates the XML into binary data, which is then sent to the server. The binary response received is translated into XML, after which the validity checks and Variable Extractors in the played request are executed.


    Home