This post originated from an RSS feed registered with Ruby Buzz
by Matt Bauer.
Original Post: ErlAMF Update
Feed Title: blogmmmultiworks
Feed URL: http://blog.mmmultiworks.com/feed/rss.xml
Feed Description: Thoughts on Ruby, hosting and more
I gave a presentation on Monday about ErlAMF. I only had the deserialization of the AMF message done at the time as I ran into a few problems. My original goal was to just code for the AMF0 protocol and leave the AMF3 protocol till later. It was a good idea until I tried to wire up the Service Browser from amfphp project. The service browser uses RemoteObject to browse the available services and so I was stuck coding in AMF3 support. It also meant delivering an alpha version for Monday wasn't possible.
So where are things right now? ErlAMF can deserialize most messages in both AMF0 and AMF3 format. Arbitrary Erlang functions can be invoke from Flex but error reporting is lacking. This leaves the serialization or mapping from Erlang back to Flex remaining. It's not too far off but I'm going to take some extra time to refactor the Erlang code into more modules. My best guess at this point is middle of next week for an alpha release.