> I am not sure if Godefroid has understood the question. This is the way I > understood it: > > ?kukitTimeStamp is something that we add as an always changing query > parameter to the POST request. Originally, we added this because we > simply wanted to make sure that the requests are never cached. However > this is coming from the very first piece of kss code, and thought to > serve no purpose any more (as it does not seem to do any harm either). > > Actually, you could probably remove it and still experience no change: as > POST requests are never supposed to be cached anyway. You need to change > the code in line 129 of serveraction.js. There is no other way to do it > at the moment then change it in the code for yourself. > > In the close future, we will be able to have both non-cachable (POST) and > cachable (GET) requests, as well as the kss parameter to set the caching > strategy on the action. This is in a very advanced state of > implementation, as the necessary changes on the framework are already > developed and waiting for review and merge. This means there is good > chance that this feature arrives in kss 1.5. > > (p.s. the kukittimestamp will disappear in any case, because we can > implement caching in a better way, with CacheFu or whatever other method.) > > This is the generic backround of ?kukitTimeStanp. Perhaps if you tell a > bit more about your use case, we can help you with more specific advice.
Thanks. Yes, cache is the task of server. Best regards Vlad _______________________________________________ Kss-devel mailing list Kss-devel@codespeak.net http://codespeak.net/mailman/listinfo/kss-devel
