You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "John Plevyak (JIRA)" <ji...@apache.org> on 2010/09/03 22:08:32 UTC
[jira] Resolved: (TS-63) InkAPI uses INK_EVENT_IMMEDIATE instead of
EVENT_CONT just because they are both 1
[ https://issues.apache.org/jira/browse/TS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Plevyak resolved TS-63.
----------------------------
Assignee: John Plevyak (was: Leif Hedstrom)
Resolution: Fixed
Converted INK_EVENT_IMMEDIATE in return value position to INK_SUCCESS.
The return values are ignored but INK_EVENT_IMMEDIATE is an event code,
not a return value so this was confusing.
> InkAPI uses INK_EVENT_IMMEDIATE instead of EVENT_CONT just because they are both 1
> ----------------------------------------------------------------------------------
>
> Key: TS-63
> URL: https://issues.apache.org/jira/browse/TS-63
> Project: Traffic Server
> Issue Type: Bug
> Components: InkAPI
> Reporter: John Plevyak
> Assignee: John Plevyak
> Priority: Critical
> Fix For: 2.1.3
>
>
> For some reason the InkAPI and the examples use INK_EVENT_IMMEDIATE as a return value
> when it should be an event argument to handleEvent. They should be using EVENT_CONT
> which just so happens to also be 1 but is a return value. it doesn't even make sense as
> INK_EVENT_IMMEDIATE is used to indicate that an eventProcessor.schedule_imm()
> has occured (hence the name) while EVENT_CONT indicates that the processor can
> call with more events as compared to EVENT_DONE which indicates that it shouldn't,
> perhaps because the Continuation nolonger exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.