[Typo3] Current date problem

[Peter Russ]

Christopher wrote:

> On 09/11/05, Peter Russ <peter.russ at 4many.net> wrote:
> 
> 
>>IMHO this definetly wrong. If there is an element on a page that is NOT
>>CACHEABLE the COMPLETE page is NOT cached.
>>
> 
> 
> _This_ is wrong. If you look at any of the *_INT objects in the TSref
> you see explanations like this:
> 
> "Now, the point is, that including a script like this lets you avoid
> disabling pagecaching. The reason is that the cached page contains the
> divider string and when a "static" page is fetched from cache, it's
> divided by that string and the dynamic content object is inserted."
> [1]
> 
> "If you create this object as USER_INT, it'll be rendered non-cached,
> outside the main page-rendering. See the PHP_SCRIPT_INT for details as
> this is the same concept used there." [2]
> 
> "You can also create this object as a COA_INT in which case it works
> exactly like the PHP_SCRIPT_INT object does: It's rendered
> non-cached!" [3]
> 
> 
> -Christopher
> 
> 
> [1] http://typo3.org/documentation/document-library/doc_core_tsref/PHP_SCRIPT_INT/
> [2] http://typo3.org/documentation/document-library/doc_core_tsref/USER_and_USER_INT/
> [3] http://typo3.org/documentation/document-library/doc_core_tsref/COBJ_ARRAY_COA_COA/

Thanks for this approach. But IMHO is very theoretically. We could 
reduce parse time by 50% when we did a redesign on macina_banner and 
used USER istead of USER_INT. The only reason was, that page WAS NOT 
cache before. You could X check and have a look at cache_pages.

Regs. Peter.

-- 
_____________________________
4Many® Services
openBC: http://www.openbc.com/go/invuid/Peter_Russ