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

Pages: [1]
Print
Author Topic: Q:When does it make sense to use Multicore over single core  (Read 10171 times)
eco_bach
Courseware Beta
Sr. Member
***
Posts: 81


View Profile Email
« on: August 27, 2009, 05:44:53 »

Hi
Could someone describe examples of when it would make sense to use Multicore over single core?
Logged
Jason MacDonald
Sr. Member
****
Posts: 243


View Profile Email
« Reply #1 on: August 27, 2009, 06:07:15 »

Honestly, you should always use multicore. Even if you have no intention of using modules, you might in the future and there is no negatives to using it. There's no reason to use the single core anymore (once it was the only option, many moons ago). It exists now only as a reference for other langauges that do not support modular programming.
Logged
dihardja
Jr. Member
**
Posts: 17


View Profile Email
« Reply #2 on: August 27, 2009, 06:18:42 »

the multicore version make sense if your application needs modularity. consider this, 2 or 3 developer is working on parts/modules of a project. all parts/modules will then integrated into the main application.

using the standard version all modules are dependent to one core. all commands, mediators or proxies of each module needs to be compiled within the main application.

using the multicore, each module can stand on its own. each module can have its own commands, mediators proxies etc. this way, the modules (swfs in flash) can be developed independently. this also makes testing more comfortable.

 
« Last Edit: August 27, 2009, 07:36:21 by dihardja » Logged
sasuke
Full Member
***
Posts: 29


View Profile Email
« Reply #3 on: August 27, 2009, 12:19:33 »

Hi
Could someone describe examples of when it would make sense to use Multicore over single core?
IMO, it really depends on the application in consideration and the kind of granularity you are seeking. For e.g. you can even have a separate core for a single view like a popup search screen in an application to keep the coupling between the search and other application screens to a minimum. Or you can even have a single facade for multiple screens which are toggled using a view-stack. In this case, the views present in the viewstack form a single functionality for your application like registration. I believe there is a sample PureMVC application to this effect on the demo page.

HTH,
-sasuke
Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2871



View Profile WWW Email
« Reply #4 on: August 28, 2009, 10:36:56 »

If you start with MultiCore, you'll never have to migrate to it when your app's functionality grows to need it. And starting with it doesn't mean you have to write everything modular. You can write it the same way you'd write a Standard version app. The only difference is the factory method on the Facade is implemented slightly differently needs a string passed to it for a name.

I suggest starting with MultiCore always if the platform you use has a port. The Standard version remains as a reference version for porting to platforms that don't support modular programming.

-=Cliff>
Logged
Pages: [1]
Print