[
https://issues.apache.org/jira/browse/QPID-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7656:
-------------------------------
Description:
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.
was:
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.
> [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: [email protected]
For additional commands, e-mail: [email protected]
