[
https://issues.apache.org/jira/browse/TS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914638#comment-13914638
]
Leif Hedstrom commented on TS-727:
----------------------------------
Huh, the MIXT / stream cache has different semantics or performance
characteristics?? Are you sure? I thought it was just a way of partitioning
things, such that you can say, allow 25% of the cache for MIXT. That much said,
I pretty firmly believe that the old implementation is very broken, because
it's not possible to write a plugin that uses a specific "MIXT" or streams
cache. This was the real problem with MIXT, some of it was implemented as
plugins, but a huge majority of changes (cache, logs, metrics, configurations)
where tightly integrated with the core itself.
> Do we need support for "streams" partitions?
> --------------------------------------------
>
> Key: TS-727
> URL: https://issues.apache.org/jira/browse/TS-727
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: Leif Hedstrom
> Assignee: Alan M. Carroll
> Fix For: 5.0.0
>
>
> There's code in the cache related to MIXT streams volumes (caches). Since we
> don't support streams, I'm thinking this code could be removed? Or
> alternatively, we should expose APIs so that someone writing a plugin and
> wish to store a different protocol (e.g. QT) can register this media type
> with the API and core. The idea being that the core only contains protocols
> that are in the core, but expose the cache core so that plugins can take
> advantage of it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
