Markus Wolff wrote: > 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.
I have no problem with that either, and in fact it was the first thing I looked at. I found it easier to debug change and update a scripted version of SOAP until I got to a point where it made sence to move it over to C. >>- Stig > > 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. This is exactly what I've wanted to do. There is a LOT more to SOAP than the serialization/deserialization and HTTP to gain true interoperability. It's faster to develop new features via script, then rewrite in C once things are worked out. Using a wrapping method as above, and having whatever C code is involved have configuratable callbacks to php script would allow for rapid development in script, and a more stable high performance version in C. Shane -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
