[TYPO3-core] RFC: Feature #10097: Use native SoapClient implementation of PHP5 only

[Marcus Krause]

Hi!

This is an SVN patch request.

Type: feature

Branches: trunk

Bugtracker reference: http://bugs.typo3.org/view.php?id=10097


Problem:
Currently EM uses native SoapClient implementation of PHP5's extension 
soap. However, there are fallbacks to PEAR:Soap and nusoap library. 
Library nusoap is embedded within module EM. There is even the 
possibility to configure which implementation to be used.

The fallbacks were necessary in PHP4, but with PHP5 there is a native 
SoapClient implementation.


Solution:
Removes nusoap library, fallback switches and methods call wrappers.
Why:
- we now have a native implementation in PHP5
- Soap calls in TYPO3 core are only made in EM; the adapter is within
   module EM; so it was never intended to provide a Soap Client
   implementation for TYPO3 extensions
- we wouldn't need to maintain the embedded library and react on API
   modifications in third-party implementations (nusoap,PEAR)
- any new options to set would need us to write or modify wrapper
   methods (missing Proxy support, I'm going to implement proxy support!)


Notes:
Also attached is file INSTALL.txt (retrieved from 
http://bugs.typo3.org/view.php?id=9745). The only modification to it is 
adding extension soap to required PHP modules.


Marcus.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: INSTALL.txt
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090111/16a81a00/attachment-0001.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 10097.diff
Type: text/x-diff
Size: 232316 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090111/16a81a00/attachment-0001.diff