[
https://issues.apache.org/jira/browse/TS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870862#comment-13870862
]
Leif Hedstrom commented on TS-656:
----------------------------------
So, out of curiosity, how much work do you expect here? I wrote up a pretty
significant amount of docs around how things works. We almost have connection
collapsing already, in fact, it's probably *better* as it is today compared to
Squid. See
http://docs.trafficserver.apache.org/en/latest/admin/http-proxy-caching.en.html#reducing-origin-server-requests-avoiding-the-thundering-herd
What's really missing here is probably something like a plugin, which controls
our existing behavior based on requests / URL patterns. I would ask you not to
implement a new system without discussing this on either the Wiki, mailing
lists or bugs. :).
> reimplement Connection Collapsing in a smooth way
> -------------------------------------------------
>
> Key: TS-656
> URL: https://issues.apache.org/jira/browse/TS-656
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Affects Versions: 2.1.6
> Environment: per discussed in IRC, we'd like to clean the current CC
> codes from trunk.
> Reporter: Zhao Yongming
> Assignee: weijin
> Fix For: 6.0.0
>
>
> we should figure out how to implement the Connection Collapsing that not so
> ugly. target for V3.1 or so.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
