The solution seems strange and it seems specially made for this module loading function in flex. Making a sub mvc just seems a lot more natural.
You mean the following idea?http://forums.puremvc.org/index.php?topic=229
Only the first posts are about what I mean, but he ruined the whole discussion with this idea to put the facade, view, model and controller in one class.
So I wanted to make a fresh topic about this.
No, Multitons are not a good solution. Most submvc's only exist temporarily and a singleton/multiton that always exist is therefor not a good choice.
There articles on this topic are very interesting:http://www.ibm.com/developerworks/webservices/library/co-single.htmlhttp://steve.yegge.googlepages.com/singleton-considered-stupid
The main 2 reasons for posting this idea are:
- Checking if someone didn't already made it.
- Checking if I'm not missing a big disadvantage of problem
If nobody made it already and nobody sees a problem in the idea I want to develop it anyway.
I've already made notes in the framework to check what I actually need to change.
And with these unit test you created I should be able to test it very easily. I think it's great that you're putting so mush time into this. It doesn't happen very often that you can discus there kind of ideas with the original creator.