You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/02/16 16:11:42 UTC
[jira] [Commented] (QPID-7656) [Java Broker] Clarify concerns of
Link and LinkEndpoint in AMQP 1.0 plugin
[ https://issues.apache.org/jira/browse/QPID-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870191#comment-15870191 ]
ASF subversion and git services commented on QPID-7656:
-------------------------------------------------------
Commit 1783244 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1783244 ]
QPID-7656: [Java Broker] Move functionality from Link to LinkEndpoint
> [Java Broker] Clarify concerns of Link and LinkEndpoint in AMQP 1.0 plugin
> --------------------------------------------------------------------------
>
> Key: QPID-7656
> URL: https://issues.apache.org/jira/browse/QPID-7656
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-7.0
>
>
> Currently, in the AMQP 1.0 layer there are classes of closely related concepts with unclear responsibilities. More specifically, there is a Link_1_0 class (and subclasses) and a LinkEndpoint class (again with subclasses). The responsibilities of the classes should be clarified and the code refactored to reflect this.
> See the current (v3) [design of the LinkRegistry|https://cwiki.apache.org/confluence/display/qpid/Link+Registry+Design] for proposed responsibilities and APIs.
> Essentially, this means moving most of the current implementation of Link into the LinkEndpoint.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org