Debugging data in Flex – Flash remoting AMF data watch

November 30th, 2005

   Currently, we rely on AMF binary format to exchange the data between client and the server.
   There are only 5 known tools to me that are able to deserialize the binary AMF data into text with a debug purpose

  • Macromedia NetConnection Debugger
  • URL: Using the NetConnection Debugger in Flex.
    Pros:
    – Free
    Cons:
    – UI sucks, difficult to treat the data.
    – No performance data of the remote call (time spent, overall data served)
    – Object hierarchy was diffcult to read, especially with large data objects
    – Debugging requires special configuration in flex-config
    – Debugging requires import of extra classes adds overhead to compiled swfs
    – Difficult to debug on production systems not configured for testing
    – It does not display other pertinent information like xml and text requests

  • Flex Builder 1.5 Network Monitor built-in
  • Pros:
    – Included in the package
    Cons:
    – Requires Flex Builder

  • Charles
  • URL: http://xk72.com/charles/flash-remoting-amf.html
    Pros:
    — it works
    — trial mode lasts for ever ( requires every 30 minutes restart)
    — UI is moreless OK
    Cons:
    –price 50$ per copy,
    –400$ site license

  • ServiceCapture
  • URL: http://kevinlangdon.com/serviceCapture/
    Pros:
    — UI is very sleak
    — Under constant development
    Cons:
    — license costs 35$ per 1 seat

  • Mkulu QA Proxy 1.0 Beta
  • URL: http://apps.mkulu.org/qaproxy/beta.shtml
    Pros:
    –Free
    Cons:
    — Cumbersome setup

    To sum up:
       ServiceCapture is the best, I would like to have this tool at my hand, but it will cost the company 7 flash developers x35$ = 220$

       Currently, we rely on AMF binary format to exchange the data between client and the server.
       There are only 5 known tools to me that are able to deserialize the binary AMF data into text with a debug purpose

  • Macromedia NetConnection Debugger
  • URL: Using the NetConnection Debugger in Flex.
    Pros:
    – Free
    Cons:
    – UI sucks, difficult to treat the data.
    – No performance data of the remote call (time spent, overall data served)
    – Object hierarchy was difficult to read, especially with large data objects
    – Debugging requires special configuration in flex-config
    – Debugging requires import of extra classes adds overhead to compiled swfs
    – Difficult to debug on production systems not configured for testing
    – It does not display other pertinent information like xml and text requests

  • Flex Builder 1.5 Network Monitor built-in
  • Pros:
    – Included in the package
    Cons:
    – Requires Flex Builder

  • Charles
  • URL: http://xk72.com/charles/flash-remoting-amf.html
    Pros:
    — it works
    — trial mode lasts for ever ( requires every 30 minutes restart)
    — UI is moreless OK
    Cons:
    –price 50$ per copy,
    –400$ site license

  • ServiceCapture
  • URL: http://kevinlangdon.com/serviceCapture/
    Pros:
    — UI is very sleak
    — Under constant development
    Cons:
    — license costs 35$ per 1 seat

  • Mkulu QA Proxy 1.0 Beta
  • URL: http://apps.mkulu.org/qaproxy/beta.shtml
    Pros:
    –Free
    Cons:
    — Cumbersome setup

    To sum up:
       ServiceCapture is a winner, I would like to have this tool at my hand, but it will cost the company 7 flash developers x35$ = 220$

    As a result: We had purchased 10 licenses of ServiceCapture tool