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

[Steffen Kamper]

Hi Ernesto,

Ernesto Baschny [cron IT] schrieb:
> 
> 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.
>

if we can't rely on this, no login would be possible, as login_challange 
is stored in $_SESSION

> 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.
> 


the reason was: get rid of use DB, serialize/unserialize etc.
What happen if you use flashmessages for php warning, then you get about 
800 messages, and you'll get max execution error or DB error because 
size, and messages are lost too.

Drupal use the GLOBALS array, it's lost after one instance, i don't see 
a problem to store it in php $_SESSION. Do you have an example where 
this could fail? Imho then no TYPO3 BE is possible at all.

vg Steffen