qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Giusti (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (PROTON-557) Include local endpoint state changes in the engine Event API.
Date Thu, 10 Apr 2014 13:17:18 GMT

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

Ken Giusti reopened PROTON-557:

After some "real world" testing on 0.7rc2, I think the implementation is incorrect, or at
least not-very-useful.

I'd rather these local events be generated by the transport when the local state change becomes
effective, as opposed to the current implementation which generates the event at the moment
the open()/close() is called.  With the current implementation, the state hasn't _functionally_

Specifically, the current behavior does something like this:

// a collector.peek() at this point returns a session local state change event, even though
the state change hasn't been fully processed.

I'd rather it be:

// collector.peek() would not return a session local state change at this point
// process the transport work queue;
// collector.peek() now returns the session's local state change.

> Include local endpoint state changes in the engine Event API.
> -------------------------------------------------------------
>                 Key: PROTON-557
>                 URL: https://issues.apache.org/jira/browse/PROTON-557
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c, proton-j
>    Affects Versions: 0.7
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>             Fix For: 0.7
> The current implementation of engine events only generates events when the remote endpoint
state changes.  For completeness and symmetry, the engine should issue separate events for
local and remote endpoint state changes. 

This message was sent by Atlassian JIRA

View raw message