[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636444#comment-13636444
]
Leif Hedstrom commented on TS-1453:
-----------------------------------
I'd probably also do what James suggested, eliminate the old code, and get rid
of the INACTIVITY_TIMEOUT option. One thing I could *possible* see is to have a
way to have both activated at any time, such that you run inactivity cop once
every 60s or some such, to clean out potentially "lost" connection. I don't
know if that can ever happen (but it did in the past). That's optional though,
and can be a different bug / RFE. But if people think having such a feature is
useful, then leave the old code, but change it to an #ifdef INACTIVITY_COP or
some such (i.e. inverse the logic on the ifdef's).
> remove InactivityCop and enable define INACTIVITY_TIMEOUT
> ---------------------------------------------------------
>
> Key: TS-1453
> URL: https://issues.apache.org/jira/browse/TS-1453
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Core
> Affects Versions: 3.2.0
> Reporter: Bin Chen
> Assignee: Bin Chen
> Fix For: 3.3.5
>
> Attachments: TS-1453.patch
>
>
> when we have O(1), then we can be enable define INACTIVITY_TIMEOUT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
