qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominic Evans <dominic.ev...@uk.ibm.com>
Subject pn_sender / pn_receiver behaviour between proton-c and proton-j
Date Thu, 12 Feb 2015 22:54:30 GMT
In proton-c pn_sender / pn_receiver in the engine will always return a brand
new link.

But their equivalents in SessionImpl in proton-j, keep a cached list of the
existing session links, and return you one of those if you already have a
link with the name you asked for - which is pretty much what pn_find_link
[3] in transport.c does in proton-c.

Assume both should match in order to satisfy the python+jython unittesting.
Which behaviour is correct?

i.e., should proton-c be updated so that the pn_sender / pn_receiver calls
do a search for an existing link on the session first or should proton-j
(jython) be updated so that pn_sender / pn_receiver always return a brand
new link, and the search for existing links is only done in the transport
code?

---

[1] session.c - http://git.io/NBod
[2] SessionImpl.java http://git.io/NBKG
[3] transport.c http://git.io/NBog




--
View this message in context: http://qpid.2158936.n2.nabble.com/pn-sender-pn-receiver-behaviour-between-proton-c-and-proton-j-tp7620199.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Mime
View raw message