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

2015-06-11 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-935:
-
Assignee: (was: 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
>  Labels: api-change
> Fix For: sometime
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)


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

2014-05-19 Thread Bryan Call (JIRA)

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

Bryan Call updated TS-935:
--

Fix Version/s: (was: 5.0.0)
   sometime

> 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
>  Labels: api-change
> Fix For: sometime
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)


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

2014-02-25 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-935:
-

Labels: api-change  (was: API)

> 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
>  Labels: api-change
> Fix For: 5.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)


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

2014-02-25 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-935:
-

Labels: API  (was: )

> 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
>  Labels: api-change
> Fix For: 5.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)


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

2013-02-25 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-935:
-

Fix Version/s: (was: 3.3.1)
   3.3.3

Wtf Brian, what does this mean? Should we fix it?

> 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.3.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
For more information on JIRA, see: http://www.atlassian.com/software/jira


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

2012-04-17 Thread Leif Hedstrom (Updated) (JIRA)

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

Leif Hedstrom updated TS-935:
-

Fix Version/s: (was: 3.1.4)
   3.3.0

Moving out to 3.3.0, please move back if there will be a fix soon for v3.1.4.

> 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.3.0
>
>
> 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




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

2012-02-17 Thread Brian Geffon (Updated) (JIRA)

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

Brian Geffon updated TS-935:


Comment: was deleted

(was: Is this report clear, or should I elaborate more?)

> 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




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

2012-01-24 Thread Alan M. Carroll (Updated) (JIRA)

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

Alan M. Carroll updated TS-935:
---

Fix Version/s: (was: 3.1.2)
   3.1.3

> 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
> 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




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

2011-10-13 Thread Leif Hedstrom (Updated) (JIRA)

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

Leif Hedstrom updated TS-935:
-

Fix Version/s: (was: 3.1.1)
   3.1.2

Moving all unassigned bugs out to 3.1.2

> 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
> Fix For: 3.1.2
>
>
> 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




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

2011-08-31 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-935:
-

Fix Version/s: 3.1.1

> 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
> Fix For: 3.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira




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

2011-08-27 Thread Brian Geffon (JIRA)

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

Brian Geffon updated TS-935:


Summary: Should EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT  
(was: Shold EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT)

> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira