[TYPO3-dev] Good news: First decrease of no_cache parameter on google

[Steffen Kamper]

Hi Elmar,

"Elmar Hinz" <elmar07 at googlemail.com> schrieb im Newsbeitrag 
news:mailman.1.1195723329.31108.typo3-dev at lists.netfielders.de...
> Hello,
>
> the good news first:
>
> I measured google hits for no_cache=1 in april, next time in Juli. The
> amount of hits has been rapidly increasing. Today you can observe a
> shrinking number of hits.
>
>   April 2007 - Juli 2007 -  Nov 2007
>
> A: 2.050.000 - 2.550.000  -  2.310.000
> B: 1.650.000 - 2.460.000  -  2.280.000
>
> A: (google.de: "no_cache=1")
> B: (google.de: inurl:"no_cache=1")
>
>
> The bad news:
>
> Known bugs of key extensions that are mainly responsible for this sitution
> have not been fixed during this time:
>
> * kickstarter
>
> The SVN version still generates new extensions with forms making use the
> no_cache parameter.
>
> * tt_news
>
> There are still several places in the code that set the no_cache 
> parameter.
>
>
> Dispite of the bad news, the awareness of developers to avoid the no_cache
> parameter seems to have grown a lot.
>
> Or is the a market share of T3 simply shrinking?
>
>
> Regards
>
> Elmar
>
>

first thanks for your investigation.
The cache problem is still a magic for most of the extension developers. i 
know there are several documents describing proper usage, but they are 
spreaded around, so i think it's very important to have one "Cache-Guidline 
for Developers" on typo3.org to give it a "official" place as reference.
Also it becomes complicate if you have a USER-plugin and you want to use 
forms etc., most developers integrate a hidden-field with no_cache (e.g. 
filter/search), so guideline should point on this
- setting a proper USER-ext
- using forms in USER
- using USE_INT in USER

vg  Steffen