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

[Popy]

2007/8/23, Elmar Hinz <elmar07 at googlemail.com>:
>
>
> It would be possible to hardcode the "L" parameter like "id" and "type",
> but
> that's not a flexible solution.

L parameter can be hardcoded, because translation handling is one of the
native typo3 features. Take a look to http://bugs.typo3.org/view.php?id=6163:)
And it is pretty simple !


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.

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


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).

This is a really good idea, wich solves the cache corruption if there's no
cHash even if there's 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)>
 * every params after the cHash (or all params if there's no cHash) should
be stored somewhere and given to USER_INTs
 * During USER_INT rendering, <uncached params> have to be merged to _GET
array
 * cHash has to be valid for cached params, or the page should not be cached
 * A proprety "additionalParams_int" has to be added to typolink"
 * 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.

Would you agree so far?


So yes, and what do you think about my solution ?

Regards.
-- 
Popy

Vulnerant omnes, ultima necat.

http://popy.sytes.net