[TYPO3-dev] Solution strategy "cHash" tunnel WAS: tslib_patcher, pp_chashchecker

[Elmar Hinz]

Hi Popy,

Popy wrote:
> 
> Note that this cHash request is made because teh cHash validity is not
> checked if there's no cHash :)

That has to be altered a little.

1) Always check, if there is a cHash   
         <NO> 
                 send default cache
         <YES>
2) Check, if cHash is valid      
         <NO> 
                  redirect to error page
         <YES>
3) Check, for cache entry  
         <NO> 
                 Build page with USER and USER_INT markers. 
                    (signed parameters)
                 Cache it. Next.
         <YES>
4) Run USER_INT objects for markers in cached page.  
                    (tunneled parameters)

> 
> d) A mechanism is needed to assign the tunneled parameters to the typolink
>> function.

> I did purpose one solution : <system params (id, type, ...)>[<cached
> params (USER)><cHash>]<uncached params (USER_INT)>

That's the natural way it could look like. But it's the job of the typolink
function to generate it. The format is nothing the user should directly
bother with. Most people will translate it with coolUri anyway.

>  * every params after the cHash (or all params if there's no cHash) should
> be stored somewhere and given to USER_INTs

Why do you want to store them? There is a server log.

>  * During USER_INT rendering, <uncached params> have to be merged to _GET
> array

That's the point!!!

>  * cHash has to be valid for cached params, or the page should not be
>  cached 

Yes. See above.

>  * A proprety "additionalParams_int" has to be added to typolink" 

The API of the extended typolink function needs to be reflected carefully,
so that it will run with the existing extensions. 

My first idea:

  New properties

* hashedParameters
* tunneledParameters

  Old property

* additionalParams => depends on the setting of useCHash if it is tunneled
or cached.

>  * maybe a preprety "config.linkVars_int" too ?
> 
> With this solution, the _GET array must be erased by typo3, to ensure that
> only cached params will be sent to cached plugins.

I didn't think about this.

> 
> Would you agree so far?

More or less in all points. :-)

Regards

Elmar