Stig S. Bakken said: > 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
Unfortunately, not all (in fact, very few) providers install that extension - as well as they don´t install many other useful but not-so- common extensions. They´ll keep it this way unless enough people ask for it. But as long as only few people know these extensions exist (in part because so few providers install them), not enough people will ask for them. The best thinkable solutions would be: a) Bundle a library like PEAR::SOAP with PHP that is modified in a way that it automatically detects if the xmlrpc-epi extension is installed. If so, PEAR::SOAP only acts as a wrapper class around the calls to the extension. Else, it uses its own, slower PHP routines. b) Integrate xmlrpc-epi support as a standard extension that is installed by default. 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
