[TYPO3-core] RFC: #9599: [felogin] Enable Caching "USER" instead of "USER_INT"

[Martin Kutschker]

Ernesto Baschny [cron IT] schrieb:
>> The situation is like this:
>>
>> If you have a FORM and the form result on one page (implemented by a
>> single plugin) then you need a USER_INT. If you start with a USER you
>> cannot switch back to USER_INT no matter what TS conditions you have.
> 
> I don't think this is true. If the condition matches, the original cache
> entry (the one with the USER object) won't match anymore and another
> rendering process will start (where the plugin is USER_INT).

Hm, so really only the condition check was wrong?

>> For this situation they have over-optimized the plugin.
> 
> Can you explain what you mean with "over-optimized"?

The plugin worked well for normal usage. It didn't after "someone"
started to fiddle with conditions to make a special case work.

>> Another simple solution is to provide another plugin (without CE) only
>> for that purpose. This would avoid complicated TS conditions (which IMHO
>> will only slow down rendering and blow up the cache).
> 
> Don't think it will slow down rendering, and it will blow up the cache
> if the target page for the FORM is the current page. If the target is a
> central "login" page, it will generate the same amount of cached pages.

At least the login page will get cached twice. Granted this is not much
overhead.

> Your simple solution also won't work, because the login-form has to be
> transformed into a "Logout-Form" as soon as the user is logged in. And
> also, if you don't have a specific target-page, your login-box also has
> to show login-errors (wrong password, etc), so it has to somehow
> transform into a USER_INT as soon as a login-attemt is made.

Then let it stay a USER_INT ;)

Masi