Each format has its benefits and drawbacks, and I was wondering if anyone has yet added amf to the list? As it turns out there is a project that does have an amf0 implementation available freely and there are a few technological tidbits that make this possible. Amf is a technology that was developed by adobe/macromedia to support remote object serialization, deserialization and messaging. There are currently two specs amf0 and amf3 and both are considered binary formats, the biggest difference between the two being that amf3 encorporates a sort of compression format to try and help keep messages small.
A man by the name of James Ward has come up with a implementation at github and there is also a pretty good explanation of how he came up with the pieces to put it together. But what does this mean for development? There are so many technologies these days that allow us to remote and “choosing” the right one may seem like a tedious and daunting task. I would like to think that ultimately, we dont really need to be selective of the technology as long as we understand the caveats, but this is not necessarily allways the case. Take flash for example, flash understands a finite amount of technology to begin with, and unless you want to write a bunch of actionscript code to do the parsing of other formats you are stuck with what already exists. This of course wouldn&squo;t be an issue if we had unlimited time and budgets, but such a thing doesn&squo;t seem to exist.