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

[Martin Kutschker]

Dmitry Dulepov schrieb:
> 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).

I'm fine with keeping the library in the Core. Just for other reasons.

>> 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 :)

Yes. But they are still only hacks - they allow easy hacking, but are
not part of the API as such. XLCASSes can even break when some internal
implementation detail has changed. Such is the fate of an XCLASS.

Backwards compatibility on API level: yes, please.
XCLASS compatibility: not needed.

Masi