qpid-proton mailing list archives

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

    [ https://issues.apache.org/jira/browse/PROTON-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965353#comment-13965353
] 

Rafael H. Schloming commented on PROTON-557:
--------------------------------------------

I'm not sure I see the functional difference between the two. Even when the transport work
queue has been processed the bytes that contain the session begin frame won't necessarily
have been written to the wire. What is the semantic you're trying to achieve here? What is
the semantic you're trying to achieve here? Can you describe the key difference in semantics
as it would impact a user of the API?

> 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
(v6.2#6252)

Mime
View raw message