I tend more towards the REST type services so CFC's aren't the best vehicle for me. Since I'm doing that API, it usually doesn't make sense for me to do another type of API strictly for Flex interfaces. Also for debugging and troubleshooting, nothing beats a human readable format. Plus when it comes right down to it, how much data are you transferring to the client? If you're transferring enough data to make a huge difference in speed across the wire, I think you're probably transferring too much data for the users' needs
On 9/5/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > A CFC will respond to web service requests and AMF without you having to do > anything. Further, if custom XML is being generated, it has to come from > somewhere. So the XML generation could stay in place but the underlying CFC > supplying the data could easily be exposed for AMF calls, allowing you to do > AMF, raw XML, and web services. The bottom line is that however else you > want to expose the data, there is no reason not to use AMF to feed a Flex > app. > > > On 9/5/07, Zaphod Beeblebrox <[EMAIL PROTECTED]> wrote: > > > > > > portability....you could use any client technology to consume your > > service if it uses xml versus amf. > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get involved in the latest ColdFusion discussions, product development sharing, and articles on the Adobe Labs wiki. http://labs/adobe.com/wiki/index.php/ColdFusion_8 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:287874 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
