[
https://issues.apache.org/jira/browse/PROTON-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-225:
--
Description:
This issue is intended to cover the Transport API redesign proposed on the
mailing list
(http://qpid.2158936.n2.nabble.com/transport-interface-changes-td7588099.html)
as part of discussions around PROTON-222. The redesign is being tracked under
this new because we probably want to implement it on a different timescale to
the PROTON-222 bug fix.
When refactoring the Java implementation, we should consider if the point when
the sent/received protocol logging is done should be changed. It should also
address the difference around the use of PN_EOS (-1) that proton-c uses to
signal that a) the engine will accept no further input and b) produce no
further output.
was:
This issue is intended to cover the Transport API redesign proposed on the
mailing list
(http://qpid.2158936.n2.nabble.com/transport-interface-changes-td7588099.html)
as part of discussions around PROTON-222. The redesign is being tracked under
this new because we probably want to implement it on a different timescale to
the PROTON-222 bug fix.
When refactoring the Java implementation, we should consider if the point when
the sent/received protocol logging is done should be changed.
Redesign Transport interface such that Transport owns the in/out buffers
rather than its client
---
Key: PROTON-225
URL: https://issues.apache.org/jira/browse/PROTON-225
Project: Qpid Proton
Issue Type: Improvement
Affects Versions: 0.3
Reporter: Philip Harvey
Assignee: Ken Giusti
Fix For: 0.5
This issue is intended to cover the Transport API redesign proposed on the
mailing list
(http://qpid.2158936.n2.nabble.com/transport-interface-changes-td7588099.html)
as part of discussions around PROTON-222. The redesign is being tracked
under this new because we probably want to implement it on a different
timescale to the PROTON-222 bug fix.
When refactoring the Java implementation, we should consider if the point
when the sent/received protocol logging is done should be changed. It should
also address the difference around the use of PN_EOS (-1) that proton-c uses
to signal that a) the engine will accept no further input and b) produce no
further output.
--
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
