[TYPO3-dev] Apache/PHP TYPO3 Caching-Module

[Bernhard Kraft]

Jigal van Hemert wrote:

> AJAX seems nice, but in the Netherlands all government websites (also
> municipal sites, etc.) must follow a set of accessibility guidelines
> which dictate that for JavaScript, Flash, etc. features at least a
> fall-back mechanism must exist.

AFAIK it is similar for government sites in Austria. The whole stuff 
available to the public must work with JavaScript disabled.


>> Of course there are still _INT objects - and if tslib_fe recognizes 
>> _INT markers in the cached content it will start generating them.
> 
> This can't be handled by an external caching server, can it?

No. This is why I would like to have something specialised for T3. But 
as I already mentioned generating _INT objects can take quite a long 
time because unserializing many cObj's can also take quite some time.
Which answers your next question:


> Is reviving a serialized "cObj" object such a heavy task? Shouldn't it 
> be comparable to letting the object generate the content as if the 
> entire page wasn't cached?

The difference between a normal page-generate-run and a cached, is that 
in the later case all cObjects must be unserialized - in the first 
simply a copy of an existing instance is made.

Making 10 copies of cObj ist a lot faster than doing an unserialize 10 
times - of course this depends on the data being stored in the cObject.



greets,
Bernhard