[TYPO3-core] RFC: Feature #10097: Use native SoapClient implementation of PHP5 only
Marcus Krause
marcus at t3sec.info
Mon Jan 12 10:36:10 CET 2009
Dmitry Dulepov schrieb am 12.01.2009 09:46 Uhr:
> Hi!
>
> Martin Kutschker wrote:
>> Then we have to agree to disagree. I'm not willing to keep all
>> internal implementation details because an extension MIGHT use it
>> although it was never meant as a public API.
>
> This change can break things. Therefore it can be vetoed. I am ready
> to veto it if necessary (we agreed that this kind of changes can be
> vetoed).
>
>> IMHO no extension has a right to XCLASS something. It's a nifty
>> feature, that can fail with any release change. Only the proper API
>> should be guaranteed to work.
>
> Every extension can XCLASS something. This is what XCLASSes are for
> :) There are some custom EM changes that can be broken by the removal
> of the library.
The according files class.em_soap.php and class.nusoap.php cannot be
extended by subclasses, at least not the TYPO3 way (XCLASSes) as the
inclusion part is missing.
Marcus.
More information about the TYPO3-team-core
mailing list