Talk:Action Message Format

What you have documented is AMF as used by RTMP, but it is more common to be interested in AMF0-style RPC messaging (and the extra wrapper objects used by Flex for this). In AMF0 RPC calls, the packet format starts with a 2 byte AMF version number (0x00 followed by 0x00, 0x02, or 0x03). After that comes another 2 byte integer for the number of headers in the packet, followed by the headers themselves - a name, "must understand" flag, and the header data. Finally, another 2 byte integer for the number of "messages" in the packet, and then the messages - a target URI, response URI, and the message data. This format is documented near the end of the AMF0 spec document from Adobe. If you're looking for examples of this, check out https://github.com/rubyamf/rocketamf/tree/master/spec/fixtures/request, which I collected for testing RocketAMF. warhammerkid (talk) 16:46, 14 November 2011 (UTC)

::That is very interesting. It would be good if we could collaborate on this. After your suggestion I have already moved a big part of the article into the RTMP article where I started a new section called 'Packet Structure'. Can you please post some formal illustration of what you re saying here so that we can integrate it? Thanks! Mmick66 (talk) 14:47, 7 December 2011 (UTC)

I noticed that someone added a note about the AMF header not being 0x03 but 0x00 0x03. My packet traces show differently so I would love to investigate further before changing it. Can whoever wrote it add his knowledge in this page please? A packet trace would also be nice Mmick66 (talk) 11:19, 6 September 2011 (UTC)

Hello fellow Wikipedians,

I have just modified {{plural:9|one external link|9 external links}} on Action Message Format. Please take a moment to review [https://en.wikipedia.org/w/index.php?diff=prev&oldid=742423898 my edit]. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20110504111101/http://exadel.org:80/flamingo to http://exadel.org/flamingo
• Added archive https://web.archive.org/web/20100224041856/http://www.themidnightcoders.com:80/products/weborb-for-java to http://www.themidnightcoders.com/products/weborb-for-java
• Added archive https://web.archive.org/web/20100121172744/http://www.themidnightcoders.com:80/products/weborb-for-net/ to http://www.themidnightcoders.com/products/weborb-for-net
• Added archive https://web.archive.org/web/20100411024035/http://www.themidnightcoders.com:80/products/weborb-for-php to http://www.themidnightcoders.com/products/weborb-for-php
• Added archive https://web.archive.org/web/20081216022105/http://framework.zend.com:80/manual/en/zend.amf.html to http://framework.zend.com/manual/en/zend.amf.html
• Added archive https://web.archive.org/web/20090227043544/http://curl.com:80/company_news010609.php to http://www.curl.com/company_news010609.php
• Added archive https://web.archive.org/web/20100613053649/http://www.themidnightcoders.com:80/products/weborb-for-rails to http://www.themidnightcoders.com/products/weborb-for-rails
• Added {{tlx|dead link}} tag to http://framework.zend.com/manual/en/zend.amf.html
• Added archive https://web.archive.org/web/20090413062041/http://www.arum.co.uk:80/amf3osgi.php to http://arum.co.uk/amf3osgi.php
• Added archive https://web.archive.org/web/20110722124649/http://djangoamf.sourceforge.jp/index.php?DjangoAMF_en to http://djangoamf.sourceforge.jp/index.php?DjangoAMF_en
• Added {{tlx|dead link}} tag to http://cakeforge.org/projects/cakeamfphp/

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{tlx|Sourcecheck}}).

{{sourcecheck|checked=false}}

Cheers.—InternetArchiveBot (Report bug) 16:45, 3 October 2016 (UTC)