RE: [PHP-DEV] Re: [PEAR-DEV] SOAP, XMLRPC and WSDL

On Thu, 2002-05-23 at 23:28, brad lafountain wrote: > One reason is xmlrpc doesn't have everything that goes along with soap. > meaning WSDL UDDI WebServiceSecurity. WSDL can be implemented through the introspection stuff in ext/xmlrpc. It's just about describing/documenting the available interfaces, right? UDDI is just a catalog service AFAIK, so that would fit better on top of the SOAP stuff. > and as far as i understand that xmlrpc doesn't work on windows. > > and with some benchmarks phpsoap so far was 3 times as fast as xmlrpc. Really? What XML parser are you using? > - Brad > > --- "Stig S. Bakken" <ssb@fast.no> wrote: > > PHP already has SOAP support bundled in the xmlrpc extension, which is > > built upon the xmlrpc-epi library that we bundle. Why can't people > > improve that instead of re-inventing more wheels in all shapes and > > sizes? When we bundle a library, we should use it. > > > > - Stig > > > > On Thu, 2002-05-23 at 17:52, Andi Gutmans wrote: > > > I think it's important to have a main stream soap implementation bundled > > > with PHP and not a zillion different implementations floating around. > > > If there is enough interest we could setup a Soap mailing list where > > > interested people could cooperate possibly basing the "official" PHP Soap > > > implementation on existing work, for example, Brad's work. As I personally > > > don't have the knowledge nor the time I'm just making the suggestion :) > > > It's up to people who are interested in this topic to move it forward.. > > > I think it would be extremely beneficial to PHP. > > > Andi > > > > > > At 17:52 23/05/2002 +0200, phpsurf wrote: > > > >hi > > > > > > > >brad lafountain is working on a Soap extension which is not far from being > > > >stable. > > > >he made a good use of WSDL ... > > > > > > > >you should have look to > > > >http://phpsoaptoolkit.sourceforge.net/phpsoap/ > > > > > > > > > > > > > -----Original Message----- > > > > > From: Markus Wolff [mailto:wolff@21st.de] > > > > > Sent: jeudi 23 mai 2002 15:29 > > > > > To: smith@dybnet.de > > > > > Cc: php-dev@lists.php.net > > > > > Subject: [PHP-DEV] Re: [PEAR-DEV] SOAP, XMLRPC and WSDL > > > > > > > > > > > > > > > Am Thu, 23 May 2002 14:57:45 +0200 schrieb "Lukas Smith" > > > > > <smith@dybnet.de>: > > > > > > > > > > > What is the current status in terms of SOAP, XMLRPC and WSDL in php? > > > > > > > > > > > > How mature are the solutions? > > > > > > When will they be ready for primetime? > > > > > > Does anyone already use them in production (that can be used to show > > off > > > > > > how great the support is) or are there any other prominent examples? > > (I > > > > > > know the pear installer uses XMLRPC and Sebastian did something with > > > > > > Googles Webservices) > > > > > > > > > > We´ve been trying to make a PEAR::SOAP webservice talk to a VB.NET SOAP > > > > > client. It does work very well when you stick to passing most primitive > > > > > datatypes around: Strings, Integers, Floats, Booleans ... > > > > > > > > > > It stops being fun when you´re trying more complex structures like > > > > > resultsets from SQL-Queries. Those could be represented and passed via > > > > > SOAP as two-dimensional arrays, and in theory you could either use a > > > > > loosely typed two-dimensional array or an array of struct to represent > > > > > that data in the VB.NET client - but we did not yet manage to make the > > > > > client recognize and deserialize the SOAP data from the PHP script. > > > > > > > > > > I have not the slightest idea where to start looking. I´ve read tons of > > > > > articles on SOAP and WSDL, but all in all, the quality of documentation > > > > > on this topic sucks. > > > > > > > > > > PEAR::SOAP itself is as good as undocumented (at least the server part) > > > > > and the documentation for .NET webservices mostly talks about > > connecting > > > > > an ASP.NET webservice to a C# or VB.NET client. When it comes to making > > > > > SOAP calls to a client/server on another software platform, or even if > > > > > you just want to use SOAP-RPC encoding instead of the default > > > > > Document/Literal encoding that .NET does, the documentation is very > > > > > uncomplete. > > > > > > > > > > Thing is, you _have_ to use SOAP-RPC encoding because PEAR::SOAP does > > > > > not yet support Document/Literal (in fact, Microsoft seem to be the > > only > > > > > ones who use this encoding method by default or even fully support it). > > > > > > > > > > I guess when it comes to maturity, all available implementations in any > > > > > language still have a long way to go. > > > > > > > > > > Regards, > > > > > Markus > > > > > > > > > > -- > > > > > *21st Media* | Consulting, Konzeption, Produktion für die Bereiche: > > > > > Markus Wolff | Internet, Intranet, eCommerce, Content Management, > > > > > Hamburg,Germany | Softwareentwicklung, 3D-Animation, Videostreaming > > > > > http://21st.de | Tel. > > > > > [+49](0)40/6887949-0, Fax: [+49](0)40/6887949-1 > > > > > > > > > > > > > > > -- > > > > > PHP Development Mailing List > > > > > <http://www.php.net/> > > > > > To unsubscribe, visit: e/ o� > > > > > M$���ƍ6]http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > > >______________________________________________________________________________ > > > >ifrance.com, l'email gratuit le plus complet de l'Internet ! > > > >vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > > > >http://www.ifrance.com/_reloc/email.emailif > > > > > > > > > > > > > > > >-- > > > >PHP Development Mailing List > > > ><http://www.php.net/> > > > >To unsubscribe, visit: > > > >http://www.php.net/unsub.php > > > > > > > > > -- > > > PHP Development Mailing List <http://www.php.net/#�ߒ�άBC� > > > �Ҋ�> > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com