You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "michael goulish (JIRA)" <ji...@apache.org> on 2015/07/17 16:47:04 UTC
[jira] [Closed] (PROTON-919) make C impl behave like java wrt
channel_max error
[ https://issues.apache.org/jira/browse/PROTON-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
michael goulish closed PROTON-919.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10
commit 4ee726002804d7286a8c76b42e0a0717e0798822
please NOTE that this change also adds #define PN_OK (0) to the list of errors in error.h
> make C impl behave like java wrt channel_max error
> --------------------------------------------------
>
> Key: PROTON-919
> URL: https://issues.apache.org/jira/browse/PROTON-919
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c, python-binding
> Reporter: michael goulish
> Assignee: michael goulish
> Priority: Minor
> Fix For: 0.10
>
>
> In the Java impl, I made TransportImpl throw an exception if the application tries to change the local channel_max setting after we have already sent the OPEN frame to the remote peer. ( Because at that point we communicate our channel_max limit to the peer -- no fair changing it afterwards.)
> One reviewer suggested that it would be nice if the C impl worked the same way. That would mean that pn_set_channel_max() would have to return a result code, which the Python binding would detect -- Python binding throws exception, python tests detect it -- so it would work same way as Java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)