To me, AMFPHP is the easiest to set up and get cracking with. Finding qualified developers would be easier than with PHPObject or WebOrb. It's easy to debug with a web debugging proxy. 1.9 (AMF3 - capable) is very fast and efficient.
If you decide to roll your own, I've worked with proprietary XML-based service layers and can say that while fast and easy to debug, they are harder to scale. Still, xml requires no serialization/deserialization and is usually faster than AMFPHP. E4X makes it easy to parse. You may also want to consider xajax http://www.xajaxproject.org/docs.php. One or more PHP classes can create AJAX request/responses; Flex can talk to them with ExternalInterface, and they can talk to Flex. This is appealing because you can bolt on another UI written in another language, and really take advantage of the DOM. As for articles comparing the different options, I found this one http://www.themidnightcoders.com/blog/2007/03/flex-remoteobject-vs-webservice.html explaining something we all know: Remoting (WebOrb or AMFPHP) is faster than WSDL. hth, Mike Britton ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
