1) Every method implemented is well documented in the WSDL
2) The component implementing the SOAP methods can validate the requests easily against the WSDL
3) The component that calls the SOAP methods has a well defined (via the WSDL again) way to serialize/deserialize into its native language
Aral's points still stand, its just there are plenty of good situations to use SOAP too.
On 11/4/06, David Holroyd <
[EMAIL PROTECTED]> wrote:
On Sat, Nov 04, 2006 at 04:01:53PM +0000, Aral Balkan wrote:
> Personally, I don't see the use of consuming web services on the
> client.
Be thankful I don't try to foist COBRA on you!
SOAP isn't a good fit for applications where the network is the
bottleneck. For most other uses, it has the advantages of being well
known and well supported.
Actually, I don't care about SOAP. It's just the transport I happen to
be using to shift my bits over the internet. If something else can give
me the same rapid development model as WSDL, bring it on!
ta,
dave
--
http://david.holroyd.me.uk/
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
