i'll take a look at my code again, perhaps it is unnecessary
to fetch a reference in the constructor. thanks cliff.

hi cliff,

i'm actually considering about your proxy principle in a case where
one proxy is dependent from another proxy. this could look like this:

public function FirstProxy( data:Object=null )
{
    super ( NAME, data );
}

public function SecondProxy( data:Object=null )
{
    super ( NAME, data );
   
   _firstProxy = FirstProxy( facade.retrieveProxy( FirstProxy.NAME ) );
}

is this a behaviour your have conceived in your framework or should two proxies communicate to each other through sending events to mediators? i think there could be cases where it is not mandatory the involve a mediator or execute a command. this would also mean that you have to register the proxies in correct order:

override public function execute( note:INotification ) : void   
{
    facade.registerProxy( new FirstProxy() );
    facade.registerProxy( new SecondProxy() );
}

i don't want to take care of the correct order in the applications startup command, so what do you think?


stephan