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

[Michael Stucki]

Hi Masi,

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

Yeah obviously.

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

True but still the general idea of the improvement was always right. The 
mistake was just that globalVar was used instead of globalString.

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

It's the most perfect solution.

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/