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  PureMVC Manifold / MultiCore Version / Re: Retrieving Proxy Between Modules on: August 04, 2008, 11:07:51
I understand now.  Thank you for the enlightenment.  Very much appreciated.

Some refactoring will be needed.   :-\
2  PureMVC Manifold / MultiCore Version / Re: Retrieving Proxy Between Modules on: August 04, 2008, 12:14:40
chitchu,

Have you considered Pipes? The solution that you are looking for may be Pipes.

Using pipes, ModuleB can send a message though a pipe connected to ModuleA requesting for the data that ModuleB wants. ModuleA can then send the data through another pipe that is connected to ModuleB.

This way, the two modules are decoupled.

Ramanuja.

Thanks Ramanuja.

We already did this appoarch, and was successful.  But I was kind of feeling like it was more of a hack or a quick fix.  So I am wondering, what is the best practice for multicore sharing proxies?

Thanks in advance.
3  PureMVC Manifold / MultiCore Version / Retrieving Proxy Between Modules on: August 01, 2008, 02:49:01
Right now, we are retrieving the proxy by having the facade instance of the other module within the module that requires the proxy.  Let's say for example, module A has a proxy called UserAccountProxy and module B needs to access the UserAccountProxy from module A. 

This is how we are doing it currently within module B:

:
var facadeA:ModuleAFacade = ModuleAFacade.getInstance ( ModuleAFacade.getKey() );
var userAccountProxy:UserAccountProxy = facadeA.retrieveProxy ( UserAccountProxy.NAME ) as UserAccountProxy;

Now my question, is there any other way to loosen the coupling between modules? A way that I don't need to import Module A's facade?

Thanks in advance.
Pages: [1]