[
https://issues.apache.org/jira/browse/TS-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680922#comment-14680922
]
Leif Hedstrom commented on TS-3426:
-----------------------------------
I agree with William, and I replied a while back on the mailing list as well.
In an ideal world, we replace all the APIs, including the ones mentioned in the
original post here. In addition, as I pointed out in email, I think there are
APIs that are very specific, such as "allow caching this even though the method
used is not allowed for caching". So I think a bit-mask (under the hood) could
be necessary?
I'm also not sure that changing the overidable config is a requirement, since
it can not be done in a compatible way. Rather, we'd mark it as deprecated for
7.0.0 and removed for 8.0.0, replace with either a new config or some other
more generic method (e.g. Options in cache.config, storage.config or Lua
scriptlets).
> Consolidate the multiple API for disabling cache
> ------------------------------------------------
>
> Key: TS-3426
> URL: https://issues.apache.org/jira/browse/TS-3426
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: Sudheer Vinukonda
> Assignee: Alan M. Carroll
> Labels: A
> Fix For: 6.1.0
>
>
> There are currently multiple API (see below) that can be used by a plugin to
> disable cache for a given transaction.
> {{TSHttpTxnServerRespNoStoreSet}}, {{TSHttpTxnReqCacheableSet}},
> {{TSHttpTxnRespCacheableSet}}
> Opening this jira to analyze whether these are redundant and consolidate if
> necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
