[TYPO3-core] [TYPO3-dev] Re: RFC #11016: Implement RSA authentication for BE and FE
Benjamin Mack
benni at typo3.org
Sun Jun 7 11:19:52 CEST 2009
Hey Dmitry,
On 07.06.2009 10:58 Uhr, Dmitry Dulepov wrote:
> Benjamin Mack wrote:
>> commited the attached patch to trunk as a followup as the initial
>> patch left some empty functions that could either be removed or
>> deprecated (but wasn't).
>
> 1. This function is not deprecated
OK. Will it ever be deprecated or should we keep the empty function forever?
> 2. Removing that line breaks XCLASSes that can reply on this
> function.
Correct, because if somebody XCLASSes the class, this person should know
what he's doing... It's all in the authority of the ext developer when
he does XCLASSes. Additionally, this file is not exactly the one class
where I know that there are many XCLASSes.
For example: The DAM XCLASSes t3lib_extfilefunc. This means that after
RFC #5203 (which was 7 months ago) the DAM is not working anymore with
trunk, because it's such a mess with the XCLASSes and it's not that easy
to add this functionality. Although DAM is one of the more popular
extensions, nobody from the devs cared about it when commiting. This
ain't critizing this commit, because I'm glad somebody had the time to
work on this feature in the first place. But it also means that we can't
worry about all the XCLASSes out there. Same thing happened with the
permissions module with TYPO3 4.2 when there was AJAX added to the
module. A popular extension broke, but because it was during alpha
phase, the extension maintainer fixed it until the final release. What's
the big issue?
Well, for how long should we keep "obsolete" functions in the Core? Will
there be 80% of empty functions in TYPO3 4.7? Will there still be calls
to empty functions all the time, for the sake of backwards-compatibility
of possible XCLASSes?
> -1 to the patch. Please, revert it and post such things as normal
> RFCs next time.
Please: Lets discuss this on -dev or on 4-3.general. It's a pain to see
such discussions rising up here in this already crowded list.
All the best,
Benni.
More information about the TYPO3-team-core
mailing list