I'm assuming you're talking about ARP. If you read through the ARP mailing list arhives, you'll find discussions on this very subject. You'll even find that there are some ARP extensions that implement what you are suggesting.
On 5/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > Sometimes when a remote service is called, more than one form may need the > data > that is received. I was thinking on changing the ModelLocator, in a way that > when a model is changed, it is automatically dispatched an event like > "[modelName]Changed". Forms who may need the data from that model just > register > to listen for the event. This way, commands don't need to alert the view, and > I > guess, it allows a better separation: > Form needs data; Form dispatch event to call for a command; command calls > remote > service; When data is received, model is updated; ModelLocator dispatches > event > alerting the change; Forms who may need the data, listen for that event and > update their contents based on a query to model locator. > > This seems logic to me, but I'm not good at design patters. What do you think? > > > João Saleiro > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > -- Chris Velevitch Manager - Sydney Flash Platform Developers Group www.flashdev.org.au _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
