Personally, I don't see the use of consuming web services on the client. First off, you cannot have any sort of hidden information in there so that rules out using this for commercial web services where you have a secret key/developer key/etc. unless you want the world to know it and use up your quotas. If you're not going to use it for third-party services, then you're probably going to use it to talk to your application server. In which case, why are you using a heavy protocol like SOAP when you could be using Remoting, REST or even good-ol' fashioned variable-encoded strings over HTTP? If you are using third-party web services, you should really be consuming them on the server side and implementing security, redundancy, etc. there.
The only use I see for consuming web services directly from the client is if you're using a completely open third-party web service. I think there are a few stock ticker services that are usually used to show off client-side web services in Flash that fit the bill! Aral On 3 Nov 2006, at 19:40, David Holroyd wrote: > Is anyone interested in making a wsdl2as tool (like the Apache AXIS > WSDL2Java tool)? > > Here's a start: > > http://osflash.org/wsdl2as > > <snip> _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
