Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: [1]
1  Announcements and General Discussion / Architecture / Re: Managing a multicore puremvc application using mvc on: August 15, 2013, 07:15:51
Hi Olaf thanks for your reply. I can't find the specific post you are referring to but yeah I was looking for an alternate way of making cores speak to each other.

My solution does indeed incorporate interfaces but also places an MVC core on top of the child cores.
In my solution there would always be a central MVC hub on top of the child cores to delegate any inter-core communication should there be any need.
2  Announcements and General Discussion / Architecture / Managing a multicore puremvc application using mvc on: August 08, 2013, 04:37:18
Hi all
I've recently began using the multicore version of puremvc and so far it looks great. I found it quite hard to get into mostly because the pipes paradigm didn't make a whole lot of sense to me. The first question that came to me was why are they not using an mvc approach to the managing of individual cores?

With this in mind I explored the possibility of setting up a multicore framework using a maincore with childcores. The maincore uses mediators to handle the childcores whereas the proxy of the main core keeps track of the id's of the childcores and keeps track of the global data. This data is split into smaller fragments which is supplied to the children.

whenever a child updates its proxy, notifications are being sent to the childcore mediator who in turn tells their viewcomponent to send the appropriate signals to their respective owners (facades). In turn whenever the child needs to receive data their owners (facades) have data injected by their respective mediator (the one from the main core). For every new child that is made the main core would create a new mediator with a unique id.

Would any1 like to share any thoughts on this approach?
Pages: [1]