You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Brian Geffon (Assigned) (JIRA)" <ji...@apache.org> on 2012/02/18 07:23:59 UTC

[jira] [Assigned] (TS-935) Should EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT

     [ https://issues.apache.org/jira/browse/TS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Geffon reassigned TS-935:
-------------------------------

    Assignee: Brian Geffon
    
> Should EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT
> ------------------------------------------------------------
>
>                 Key: TS-935
>                 URL: https://issues.apache.org/jira/browse/TS-935
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>    Affects Versions: 3.0.1
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>             Fix For: 3.1.3
>
>
> When trying to use TSContCall with event = TS_EVENT_TIMEOUT I stumbled upon the fact that the API will decrement the event count for EVENT_INTERNAL or EVENT_IMMEDIATE (see INKContInternal::handle_event_count), but shouldn't we be able to do a TSContCall with TS_EVENT_IMMEDIAITE or TS_EVENT_TIMEOUT because as of now doing so would cause m_event_count to become -1 or shouldn't these defined values be something different? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira