On 02/22/2011 05:12 PM, Joshua Tolley wrote:
That does, and is kinda what I was thinking we'd have to do. For instance, some of our business logic said, "Given the presence of various application-specific headers or cookies, use the cache where normally we wouldn't, or alternatively, don't use it where we typically would." I assume the technique in this case would be to modify headers at some point in the process such that TS would decide to cache the response on its own?
Right. We have some "canned" configuration options available in records.config and cache.config, to do some of this, but specific rules like you describe more likely than not will require a custom C/C++ plugin (at least until we finish the LUA plugin, and it shows reasonable performance).
-- leif
