Home/ Questions/Q 117309
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T03:18:57+00:00

I’ve designed an MVC that doesn’t allow communication between Views (forms). If a form

  • 0

I’ve designed an MVC that doesn’t allow communication between Views (forms). If a form needs to communicate with another form, it raise an event on the controller, which other forms can subscribe to. The general idea is to keep paths of communication to a minimum, helping keep complexity down. Each View communicates with the RootController, which is a singleton, or a subController, which the View accesses through the RootController. Again, it keeps communicate paths down because everything goes through the RootController.

Does this follow general network theory in which the more nodes you add to a network, the more complex it gets. ‘And’, the more each of these nodes communicate directly, the more complexity introduced into the network. Can anyone point out what exactly this area/theory is called? References?

Is what I’m doing with the MVC analogous to having all nodes on the network go through a central node to communicate with each other?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I think you may want to look up graph theory (which is the basis for network topology).

    And your solution does sound like it is analogous to having everything communicating through a central node in a network. This is a good pattern for simplicity (each new node only needs one connection to connect to everything) but is bad for scalability as you will reach a point where the amount of work your RootController is doing is huge. Each new node brings you closer to having a major performance bottleneck in your central node.

    • 0