One reason is because SOAP carries significant overhead whose purpose is to make the interface discoverable by anonymous third parties. Event though it is "built-in" a lot of complex code is generated to support SOAP. While, with REST, you do have to code some xml generation, that code is pretty straightforward and simple.
Also, straight xml is easier to work with in Flex than the heavily wrapped and namespace littered xml from a SOAP call. I say if you don't need SOAP, don't use it. Just an opinion, of course. Tracy ________________________________ From: flexcomponents@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Samuel R. Neff Sent: Tuesday, June 26, 2007 11:26 PM To: flexcomponents@yahoogroups.com Subject: RE: [flexcomponents] Flex 3 and asp.net 2.0 webservices Getting even more off topic here.. :-) Why would you suggest using REST instead of SOAP when both .NET and Flex have built-in SOAP support whereas REST usage implies direct XML coding which web services are designed to abstract away? I'd be all for using REST when it's built-in to both .NET and Flex, but since there are built-in alternatives that work today without extra work, I don't understand promoting it for Flex/.NET integration. Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] ________________________________ From: flexcomponents@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Marc Bir Sent: Tuesday, June 26, 2007 11:12 PM To: flexcomponents@yahoogroups.com Subject: RE: [flexcomponents] Flex 3 and asp.net 2.0 webservices Flex Components is not really the right place for a Flex 3 beta discussion... but having said that the first place I would look is the CrossDomain xml file (or whatever it is called) that is required for Flash to talk to servers other than local. We had a similar issue with a Flex 2 app at work talking to a .NET service. In addition ASP.Net 2 adds several enhancements to the webservice core libraries that make it much more robust, but from your example it does not appear to be an issue. Would probably help if you had included the exact error message you receive when making the request. Something else to consider is using a REST service instead of a SOAP service for simplicity (and REST is just better anyways ;) Downloading Flex 3 beta now, but I urge you to hit up FlexCoders or one of the other groups, as this group is specifically about creating components for the Flex framework. Hope I helped somehow, -Marc
