[
https://issues.apache.org/jira/browse/TS-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919126#comment-13919126
]
ASF subversion and git services commented on TS-2522:
-----------------------------------------------------
Commit 4f0b0b447ed76244287ae5385719fc56b3385a24 in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=4f0b0b4 ]
TS-2522 Update the docs with new default conf dir
> Rewrite header_rewrite hook management
> --------------------------------------
>
> Key: TS-2522
> URL: https://issues.apache.org/jira/browse/TS-2522
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 5.0.0
>
>
> Right now, we use a transaction slot to pass information from "remap" state
> over to one of the normal hooks. Because of the way this plugin works, I
> think this can be optimized away. What we should do is to have one "global"
> continuation for each remap rule, and schedule it from the remap plugin.
> This avoids having all the global hooks checking the transaction state (slot)
> every time. It's also very cheap to schedule a transaction hook, it's O(1)
> simply appending it to a linked list of hooks. If the hook doesn't get
> invoked, it's mostly a no-op.
> Finally, this avoids consuming one of the limited transaction hooks, and at
> the same time reduces overhead by only executing hooks when necessary.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
