[TYPO3-dev] new extension: vx_xajax_shoutbox

Ernesto Baschny [cron IT] ernst at cron-it.de
Tue Jul 18 15:56:16 CEST 2006


Elmar Hinz schrieb am 18.07.2006 13:49:

>> it was USER_INT in the first time. But i'm not sure why not to cache
>> this one. JavaScript is doing his job and it seemed to work out...
> 
> Interesting point. How does it come that you can do dynamic requests to a
> static cached page?
> 
> One theory:
> 
> The first call of the whole page always delivers the same result and can be
> cached. For this USER is o.k.
> 
> But what about the dynamic requests by xajax? They come with a special
> xajax parameter. So another version of the page is build. Before it can be
> cached xajax sends the response xhtml directly to the browser and exits.
> Right before the page gets the chance to be cached. So USER doesn't matter
> here.

If you are using eID you don't have to worry about TYPO3 caching at all.

If you use the approach of handling your ajax responder in a PAGE object
with a different typeNum (say 91), you can just disable caching in this
page object altogether. Something like that:

ajax = PAGE
ajax.typeNum = 91
ajax.no_cache = 1
ajax.10 < plugin.tx_yourplugin_pi
ajax.10.isAjax = 1

You just have a problem if you are handling your ajax response in the
same PAGE/pid/plugin environment as your regular script (which is either
an USER or an USER_INT. But I wouldn't recommend that anyway.

Cheers,
Ernesto





More information about the TYPO3-dev mailing list