[TYPO3-core] RFC #12130: Improve performance of flashmessages

[Ernesto Baschny [cron IT]]

Rupert Germann schrieb:

> Steffen Kamper schrieb:
>> One thing: template::pushFlashMessage could be removed as well, and
>> the calls could be changed to call t3lib_messagequeue direct. As this
>> wasn't released, we don't need this wrapper.
> 
> good point.
> done in v4.

I have only seen $_SESSION being used in user authentication
(challenge-response) and session_start's are hidden inside some
functions, so that I don't really know if we can rely that we always
have a PHP session available.

This is at least not very TYPO3-like, and usually we use our "own"
session handling methods:

$BE_USER->getSessionData($var);
$BE_USER->setAndSaveSessionData($key,$val);

Well, this is what was being used before (in template.php). And it is
currently stored in the database, meaning the session survives
"cross-webserver boundaries", which might be useful on multi-web-server
environments with one DB-backend.

So I suggest to keep it like it, don't use $_SESSION and then open
another issue where the $BE_USER session handling can be configured to
use PHP's session instead of our own be_session table in DB.

Cheers,
Ernesto