> 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.
Sounds like the way to go. This way everybody can use it and gain optimal performance from their environment and developers don't have to worry about it either. Hopefully someday we will be able to do the same with MDB (or atleast with large chunks of it) Mit freundlichen Grüßen, 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] -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
