You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2018/10/10 15:37:00 UTC
[jira] [Resolved] (DISPATCH-1133) Router core modules for Core
extensions
[ https://issues.apache.org/jira/browse/DISPATCH-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved DISPATCH-1133.
--------------------------------
Resolution: Fixed
> Router core modules for Core extensions
> ---------------------------------------
>
> Key: DISPATCH-1133
> URL: https://issues.apache.org/jira/browse/DISPATCH-1133
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 1.4.0
>
>
> Introduce a formal notion of Router Core Module. Such a module is an extension to the router core engine. The purpose of establishing core modules is to isolate new functionality into a separate module file, rather than embed it into the heart of the core files (which has happened too much).
> The first core module is the test-hooks module used to aid in the testing of the various core APIs (like the core_endpoint API). Modules shall be used in the core extensions related to the Edge Router feature.
> In the future, existing capabilities can be moved into modules to provide better code organization in the core. The management agent is a good candidate for this. Link-routing can also be moved out to a core module.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org