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 / General Discussion / Questions about some design decisions regarding proxies on: March 03, 2009, 01:22:44
Hi All,

I've been reviewing PureMVC, and have a few questions about its architecture:

  • Why do proxies have names?  I suspect this is to prevent multiple proxies of the same name from being registered.  What is the functional benefit of this, however?  Why not let users to register multiple proxies of the same class with different names, and decouple this view-specific logic from the proxies themselves?
  • Why should proxies be required to expose their data object?  Is this not an implementation detail?  I understand that a very common subset of cases will map a proxy directly to an object, but this is by no means the dominant case, and again I question why this object must be exposed at all.

Aside from this, I find PureMVC to be a very well-engineered library and would like to thank all its contributors for their hard work.

Pages: [1]