You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/02/25 01:45:05 UTC
[jira] Created: (QPID-391) Refactor Java Broker into layers to
handle multiple versions of AMQP
Refactor Java Broker into layers to handle multiple versions of AMQP
--------------------------------------------------------------------
Key: QPID-391
URL: https://issues.apache.org/jira/browse/QPID-391
Project: Qpid
Issue Type: Task
Components: Java Broker
Reporter: Rob Godfrey
Assigned To: Rob Godfrey
0-9WIP and, more particularly the upcoming 0-10 releases of AMQP will result in major changes to the wire level encoding, and semantic model of AMQP. However the core functionality of the broker will not need to greatly change.
The broker code must be refactored to properly separate separate layers of responsibility. This will, as a consequence, allow us to support multiple versions of the protocol within the same broker implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-391) Refactor Java Broker into layers to
handle multiple versions of AMQP
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-391:
--------------------------------
Fix Version/s: M3
> Refactor Java Broker into layers to handle multiple versions of AMQP
> --------------------------------------------------------------------
>
> Key: QPID-391
> URL: https://issues.apache.org/jira/browse/QPID-391
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Rob Godfrey
> Assigned To: Rob Godfrey
> Fix For: M3
>
>
> 0-9WIP and, more particularly the upcoming 0-10 releases of AMQP will result in major changes to the wire level encoding, and semantic model of AMQP. However the core functionality of the broker will not need to greatly change.
> The broker code must be refactored to properly separate separate layers of responsibility. This will, as a consequence, allow us to support multiple versions of the protocol within the same broker implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-391) Refactor Java Broker into layers to
handle multiple versions of AMQP
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey resolved QPID-391.
------------------------------
Resolution: Fixed
Fix Version/s: (was: M3)
M2.1
> Refactor Java Broker into layers to handle multiple versions of AMQP
> --------------------------------------------------------------------
>
> Key: QPID-391
> URL: https://issues.apache.org/jira/browse/QPID-391
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: M2.1
>
>
> 0-9WIP and, more particularly the upcoming 0-10 releases of AMQP will result in major changes to the wire level encoding, and semantic model of AMQP. However the core functionality of the broker will not need to greatly change.
> The broker code must be refactored to properly separate separate layers of responsibility. This will, as a consequence, allow us to support multiple versions of the protocol within the same broker implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.