Mailing-List: contact proton-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: proton@qpid.apache.org
Date: Thu, 10 Apr 2014 17:54:16 +0000 (UTC)
From: "Ken Giusti (JIRA)" <jira@apache.org>
To: proton@qpid.apache.org
Message-ID: <JIRA.12707197.1396972467551.94520.1397152456921@arcas>
In-Reply-To: <JIRA.12707197.1396972467551@arcas>
References: <JIRA.12707197.1396972467551@arcas>
Subject: [jira] [Closed] (PROTON-557) Include local endpoint state changes
 in the engine Event API.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ken Giusti closed PROTON-557.
-----------------------------

    Resolution: Fixed

Re-closing - the modification I proposed would not add any additional guarantees to the interpretation of the state change as it is now implemented.

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