Yeah, I keep seeing PHP SOAP and XMLRPC being announce packages everywhere. But incompatible API's will not benefit PHP much and the efforts are simply redundant.
I think it would make sense to create such a mailinglist. As I am still fairly busy with working on a merge of Metabase and PEAR DB called MDB (blatant plug :-) ) I can't spend as much time as I would wish on this topic. For now I will try to order the feedback I get and put together a little static page with the content. Basically I will take every package I find and list it there and put any comments people send regarding that package underneath. Best regards, Lukas Smith [EMAIL PROTECTED] _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de [EMAIL PROTECTED] > -----Original Message----- > From: Andi Gutmans [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 23, 2002 5:53 PM > To: phpsurf; Markus Wolff; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: [PHP-DEV] Re: [PEAR-DEV] SOAP, XMLRPC and WSDL > > 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:[EMAIL PROTECTED]] > > > Sent: jeudi 23 mai 2002 15:29 > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: [PHP-DEV] Re: [PEAR-DEV] SOAP, XMLRPC and WSDL > > > > > > > > > Am Thu, 23 May 2002 14:57:45 +0200 schrieb "Lukas Smith" > > > <[EMAIL PROTECTED]>: > > > > > > > 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: 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/> > 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
