A couple of things: first of all, I’ll work on the docs whenever possible, that Captivate license will be put to good use. Second of all, I’m not sure AMFPHP will reach 1.0 final. It may just skip straight ahead to AMFPHP 1.1, or even 2.0. Why?

Well, two major things have come along that make me think that AMFPHP 1.0 is just the beginning. First of all, there’s a new AMF in ActionScript 3 called AMF3, and I’ve been told that we’re not compatible with AMF3 just yet. So a new round of reverse-engineering (or “discovery” as others have put it) will be started in order to get to the bottom of this exciting new addition. Who knows? Maybe AMF3 will allow us to send BitmapData objects over the wire; maybe it will do all sorts of crazy voodoo. I have no idea, but I am going to attempt to write it in by the time Flex 2 beta comes to town.

Another major development: a contributed CakeAmfphp build by one of the Cake developers, gwoo, aka Garrett J. Woodworth. Cake, for those who don’t know, is a Ruby on Rails-inspired framework for PHP that is getting a lot hype. Basically the build is a merge of AMFPHP with Cake functions built-in; I haven’t dug into it much but so far it looks fantastic for two reasons: Cake classes can be used to optionally output HTML as well, and Cake speeds up development tremendously. gwoo’s effort will hopefully be repackaged and available either in the core or as a drop-in add-on to AMFPHP (or the other way around, a drop-in add-on to Cake).

I am really digging Fusebox these days too, so don’t be surprised if a future version of AMFPHP drops the methodTable and introduces a circuit.xml-like mechanism.

In short, lots to come for good old AMFPHP!