[
https://issues.apache.org/jira/browse/PROTON-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464703#comment-13464703
]
Rob Godfrey commented on PROTON-21:
-----------------------------------
I'm holding off on applying this until the work in moving the Java API over to
the new design for "Transport" is in place to bring it into line with the C.
At that point the way to integrate with code which requires a "frame level"
transport should be clearer and hopefully provided in such a way as to be
identical between the Java engine and the C engine.
I'm hoping to get the API stuff up to date in the next few days.
Overall I think the goal here is to ensure that the Java and C provide
identical interfaces and not to create APIs which are Java specific.
Apologies for my tardiness in this, have been distracted by other day job
issues, but should have more time available going forward
> Extract the logical AMQP frame handling to an AbstractConnectionHandler
> -----------------------------------------------------------------------
>
> Key: PROTON-21
> URL: https://issues.apache.org/jira/browse/PROTON-21
> Project: Qpid Proton
> Issue Type: Improvement
> Reporter: Hiram Chirino
> Attachments: PROTON-21-v3.patch
>
>
> Right now all the logic that handles logical AMQP frame events is inside of
> the TransportImpl class. That interface only allows you to pump bytes in and
> out of the connection. If we extract all the handling logic to an
> AbstractConnectionHandler you should be able to use that directly and pump
> logical AMQP frames and avoid the frame encoding/decoding phase that the
> TransportImpl also does.
--
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
