You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2013/03/07 15:16:13 UTC

[jira] [Resolved] (PROTON-264) Proton-J and Proton-C transports make inconsistent use of return values within methods input and output

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

Keith Wall resolved PROTON-264.
-------------------------------

    Resolution: Fixed

Change committed at rev. 1453849
                
> Proton-J and Proton-C transports make inconsistent use of return values within methods input and output
> -------------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-264
>                 URL: https://issues.apache.org/jira/browse/PROTON-264
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c, proton-j
>    Affects Versions: 0.4
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: 0.5
>
>
> This defect refers to the transport interface already in the process of being deprecated by PROTON-225.  The scope of PROTON-225 has been increased (=noted in Jira) to ensure that this defect is not carried forward to the new interface and we end up with consistent behaviour.
> Currently, in Proton-C pn_transport_output() returns PN_EOS (=-1) to signal that the Transport will produce no further output, and  pn_transport_input() returns PN_EOS to signal that the Transport will accept no further input.   However, Proton-J, output always returns the number bytes output (even if zero), and input returns the number of bytes accepted (again even if zero).
> This difference presents a problem to tests utilising the Proton-JNI binding.   As a temporary workaround, JNITransport class will changed to hide this difference from the caller.

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