I'm not blanket dismissing SOAP. I am just saying that web services should be consumed *on the server*, not the client (on untrusted networks.) In such a scenario, it's much better to consume the web service on the server and expose it to the client in a more efficient manner (for example, Flash Remoting.) This way, you can transmit information securely and implement redundancy.
Robert brought up use cases that I hadn't considered (kiosks, etc.) where I wouldn't have such an objection. Aral > I disagree with your blanket dismissal of SOAP. Yes, it's heavy and > not suitable for all situations, but when you need to send complex > object back and forth to a web service then there's nothing that beats > SOAP. > <snip> _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
