You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ernest Allen (JIRA)" <ji...@apache.org> on 2016/10/24 22:19:58 UTC
[jira] [Created] (DISPATCH-543) Initial load of topology page
fetches too much information
Ernest Allen created DISPATCH-543:
-------------------------------------
Summary: Initial load of topology page fetches too much information
Key: DISPATCH-543
URL: https://issues.apache.org/jira/browse/DISPATCH-543
Project: Qpid Dispatch
Issue Type: Improvement
Components: Console
Reporter: Ernest Allen
Assignee: Ernest Allen
As the topology graph is created, several entities for each router are fetched:
- .connection
- .router.link
- .router
- .router.node
For large numbers of routers this takes a while.
Break up the creation of the topology graph. The routers and their connections to other routers can be generated using only .connection information.
.router-link is used:
- to draw the small client circles. After the initial graph is drawn, go back and fetch the .router.link info for any router that has connections that are not "inter-router".
- to display the popup when a client is clicked. This can quickly be fetched for the individual router when one of it's clients is clicked.
- to display the cross-section popup. This can be fetched when needed.
.router.node is used to generate the highlight line between routers. This entity can be fetched when needed.
.router is used when adding a new node. This can be fetched when needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org