Re: phpdoc and web services

From: Date: Tue, 29 Jan 2002 00:41:15 +0000
Subject: Re: phpdoc and web services
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-4269@lists.php.net to get a copy of this message
Hello, Lukas Smith wrote: > > Actually SOAP and WSDL are not interlinked at all > > SOAP can be described via WSDL > WSDL can use SOAP as its binding > > But it does not have to be that way > There are some similarities though: > > - both use XML schema (although SOAP extends XML Schema to also include > array's and structs) > - both sort of recommend each other > > But WSDL can of course also be used along side with XML-RPC. > > BTW: Actually after having read about SOAP and XML-RPC I am beginning to > like XML-RPC more and more. XML-RPC is much simpler. It is feature > frozen since quite some time. It does not include crazy "routing" stuff > that SOAP includes through their header/node concepts but can obviously > be extended to do everything that SOAP can. I think that in the end only one stardard will prevail because both attempt to do the same. I noticed that some people fight against SOAP because they assume that it is just yet another Microsoft thing. I don't cheer for Microsoft, nor SOAP is just yet another Microsoft thing, but I think that in the end SOAP will be what prevails precisely because Microsoft only supports SOAP in their products and languages, so you will see more people providing Web services via SOAP than XML-RPC. Being feature frozen is not a good thing IMHO because standards need to evolve to support real world needs. I think it is more important to provide backwards compatibility to software that relies in older versions of the standard. Are you stuck with HTML 1.0? I think that if you need HTML 4.0 features you will use them anyway. Still, pages written in HTML 1.0 can still be viewed and that is what matters. The same for SOAP older versions that should be accessible by newer version SOAP clients. Regards, Manuel Lemos

« previous php.pear.dev (#4269) next »