[TYPO3-dev] Performance optimization Typo3

[Ernesto Baschny [cron IT]]

Hi Chris,

great to hear that. Please submit your improvements in the Issue tracker
(http://bugs.typo3.org/). You can attach your patches there. Point to
your issue # in this thread.

Cheers,
Ernesto

Chris Zepernick {SwiftLizard} schrieb am 17.08.2010 11:48:
> Hi,
> 
> found a nice way to do that centralized,...
> will provide you with the patch and the other stuff this
> evening...
> 
> cheers
> 
> chris
> 
> 
> Am 17.08.10 11:31, schrieb Chris Zepernick {SwiftLizard}:
>> Hi
>>>
>>> now (I think) I've got it. That is indeed not so beautiful. Feel free to
>>> provide a patch to improve that situation.
>>>
>>> I would suggest to add methods to switch the user's session (back and
>>> forth) to class.t3lib_userauth.php and use those in the beuser hooks
>>> module (to switch to user) and logoff hook (to switch back).
>>>
>>> What do you think?
>>
>> That sounds like a nice plan ;-)
>>
>> With the solutions I will send to you, I'll try to provide such a
>> solution too.
>>
>> cheers
>>
>> chris
>>
>>>
>>> Cheers,
>>> Ernesto
>>>
>>> Chris Zepernick {SwiftLizard} schrieb am 17.08.2010 10:59:
>>>> Hi guys,
>>>>
>>>> I think you got me slightly wrong.
>>>>
>>>> I've got no problem with the first 4 classes
>>>> and their hierarchie they work totally fine for me,
>>>> although there could be some improvements made ;-)
>>>>
>>>> The inconvinience came from the hook in sysext/beuser
>>>> for switch back, and from the index.php in this "Extentsion"
>>>> where the switch user is implemented.
>>>>
>>>> Both alter the current users session data by querying the database
>>>> themself instead of using methods from the auth classes.
>>>>
>>>>
>>>> Regards
>>>>
>>>> Chris
>>>>
>>>> Am 17.08.10 08:19, schrieb Dmitry Dulepov:
>>>>> Hi!
>>>>>
>>>>> Chris Zepernick {SwiftLizard} wrote:
>>>>>> Last inconvinience we discovered was that the whole user auth
>>>>>> process is
>>>>>> spread accross 4 classes, if you take the switch user function in
>>>>>> BE into count we have 6 places to change.
>>>>>
>>>>> Switches like this are bad and show that classes are not properly
>>>>> split by
>>>>> functionality. -1 to that. Please, keep classes well separated and
>>>>> without
>>>>> such switches.
>>>>>
>>>>> +1 to the performance enhancements in general. :)
>>>>>
>>>>
>>
>