[
https://issues.apache.org/jira/browse/TS-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Galić updated TS-484:
--------------------------
Description: it seems that the logic around the new API
TSHttpTxnSetRespCacheableSet() is very similar to the old, existing
TSHttpTxnServerRespNoStore(). Would it be possible to "merge" the new API logic
into the existing one (without changing the old API) ? This would be a great
thing to fix before we finalize v2.2, to avoid breaking / adding more APIs.
(was: it seems that the logic around the new API
INKHttpTxnSetRespCacheableSet() is very similar to the old, existing
INKHttpTxnServerRespNoStore(). Would it be possible to "merge" the new API
logic into the existing one (without changing the old API) ? This would be a
great thing to fix before we finalize v2.2, to avoid breaking / adding more
APIs.)
> TSHttpTxnSetRespCacheableSet() vs TSHttpTxnServerRespNoStore()
> --------------------------------------------------------------
>
> Key: TS-484
> URL: https://issues.apache.org/jira/browse/TS-484
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: Leif Hedstrom
> Fix For: 5.0.0
>
>
> it seems that the logic around the new API TSHttpTxnSetRespCacheableSet() is
> very similar to the old, existing TSHttpTxnServerRespNoStore(). Would it be
> possible to "merge" the new API logic into the existing one (without changing
> the old API) ? This would be a great thing to fix before we finalize v2.2,
> to avoid breaking / adding more APIs.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
