Currently the GraphContainer has direct access to the underlying TopologyProvider. Each GraphContainer represents a user session, where as the TopologyProvider itself is a singleton object. This means that each user can actively refresh the underlying TopologyProvider. This is very bad for performance, especially as the Topology is refreshed in the following circumstances:

• Icon reset

• Change of Meta-TopologyProvider

• Refresh now (or automatic refresh)

The current implementation should be refactored in such a way, that the GraphContainer does not have direct access to the underlying (Meta-)TopologyProviders. A TopologyService instead should be handling the refresh on a regular basis. The user always only gets a copy of the view, when accessing the data.