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

That is wrong. Conditions are always checked before the page is fetched 
from the cache. So with the help of a condition, you can cache the same 
page ID multiple times.

(Background: In tslib_fe, $this->all is built which contains all 
conditions that matched, among some more information. The md5sum of this 
serialized array is then used to fetch a record from cache_pagesection. 
This means, if conditions are different there can be multiple records 
stored in cache_pagesection. It also means that you can easily blow it 
up when using too many conditions...)

Skipping the rest since this is not the case anyway :-)

- michael

> Now typo3.org and many others want to have a "login box" on *every* page
> of their site. As the form action redirects to another page they
> naturally want a USER object.
> 
> For this situation they have over-optimized the plugin. IMHO it'd be
> simple for them to set the type USER into the TS configuration. If the
> "login box" is embedded in the layout it will be hard-coded anyway.
> 
> 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).
> 
> Perhaps it's also possible with the plugin code by the USER/USER_INT
> switches. Or maybe you can use a URL with a cHash as form action that
> makes the plugin render itself als USER_INT.
> 
> Masi


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