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

[Elmar Hinz]

> IMHO there are 2 options for a clean cHash system:
>>
>> a) Only check for cHash if the cHash has been sent else deliver the
>> default
>> cache.
>> b) Always send a cHash, but "tunnel" or "bybass" parameters for USER_INT.
> 
> 
> +1 for the "tunnel", and i'm ready to help core team (if they need)
> 

Hi Popy,

good. I also come more and more to the conclusion that a "tunnel" is not
only an option but a necessary part of the solution. It's required to be
able to send "non-caching USER_INT parameters" and "caching parameters"
like language parameters at the same time by a link.

It would be possible to hardcode the "L" parameter like "id" and "type", but
that's not a flexible solution.


So this is the current state of my "cHash solution specification":

a) Automatically check and cache, if a cHash has been sent. Else deliver the
default page from cache. Drop the rule, to request cHash from inside USER
objects completely.

b) The typolink function has to sign all parameters, that are not to be
tunneld, by a cHash.

c) The unsigned, tunneld parameters are only offered to USER_INT (during
marker replacement phase).

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

Would you agree so far?

Regards

Elmar