Mailing-List: contact proton-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: proton@qpid.apache.org
Date: Tue, 24 Sep 2013 14:48:06 +0000 (UTC)
From: "Darryl L. Pierce (JIRA)" <jira@apache.org>
To: proton@qpid.apache.org
Message-ID: <JIRA.12670289.1380033909964.9551.1380034086232@arcas>
In-Reply-To: <JIRA.12670289.1380033909964@arcas>
References: <JIRA.12670289.1380033909964@arcas>
Subject: [jira] [Assigned] (PROTON-427) settle does not match accept/reject
 for ruby
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Darryl L. Pierce reassigned PROTON-427:
---------------------------------------

    Assignee: Darryl L. Pierce
    
> settle does not match accept/reject for ruby
> --------------------------------------------
>
>                 Key: PROTON-427
>                 URL: https://issues.apache.org/jira/browse/PROTON-427
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.5
>            Reporter: Gordon Sim
>            Assignee: Darryl L. Pierce
>
> In 0.4 the ruby versions of accept()/reject() and settle() all took a tracker and flags (and both were required)
> In 0.5 this was changed for accept/reject. Only one argument could be passed, the tracker, and it was optional. However settle remains the same as before which seems inconsistent. (Of course changing it now would break the API again between 0.5 and the next release).

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