[TYPO3-dev] set_no_cache is bad. What's next?

[Dmitry Dulepov]

Hi!

Franz Holzinger wrote:
> But does this really work? When a USER object is cached, then normally
> the plugin is not called any more. But how should the USER_INT part of a
> USER object be changed then?
> Maybe it has always to be one USER object called by a USER_INT object.

The idea is that you can convert USER to USER_INT *when* USER is executed at the first time. For example, if you have a TS property in your plugin to make it non–cached, you could check that property and if it is set to "1", you just make USER_INT out of USER. This will work because USER will be executed at that moment.

>> The point is that you create from the search query (piVars) a key for
>> the search result. Whenever the PI has to show a result it will look
>> it up in the search cache. In this cache only the ids of the found
>> rows are stored (sorted!).
> How do you implement a search cache?

This is a different question :) There is a lot of ways to implement search cache. The simplest is to store the hash of the query together with a serialized list of ids.

-- 
Dmitry Dulepov
Facebook: http://www.facebook.com/dmitryd
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs