We have Flash/.NET applications that remain inside our secure firewalls for other interal employees to use, and so security is not so much of a concern. We have found SOAP calls to .NET methods from flash to be a fantastic way to quickly build a large RIA app quickly. Communication between a Flash developer and an .NET developer has been simple and changes can be made quickly. While SOAP may be bloated due to it's XML format, we have been able to deal with any minor performance lags. I have built tests with Flash Remoting, and while it worked, it seemed too complex in setup and development effort compared to Webservices for our purposes. For building a large RIA app, SOAP Webservices has been awesome. It's so friggn' easy to pass complex data sets and call methods on the server. My .NET developer builds a complex object - I read that object, allow the user to change it, and send the object back and so on. Long live SOAP! :) I'm not dismissing your points, just providing another scenario besides a kiosk app where SOAP development has seemed to be the best choice in a given situation. I have no doubt there are plenty of situations where using SOAP to transmit data would be a bad choice.
Jason Merrill Bank of America Learning & Organizational Effectiveness _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
