thanks cliff... that is the answer that i was looking for.  i was unsure if removing a view managed by the mediator meant to remove the mediator as well... knowing it may still be interested in responding to notifications sent by throughout the life of the application.

what i have been doing is registering the mediators once when there first view is displayed.  then when it is needed again during the use of the application, the mediator can manage the adding/removal of the views it needs to display.

thanks for the response!!!

hi all,

i am new to MVC, only a few months experience... but i have worked with AS2 and AS3 for a long time.  i am used the PureMVC framework for the latest version of our product.  i have several nested views with a combination of components.  i am using "mode" and "view" changes to manage different form states and it works great right now to help manage and remove the child views... but when do i remove a mediator for a view?  is it hurting anything to allow a mediator to persist in the application if it only acts on notifications it is interested in?  seems like on register if i great a view for the first time, i can use notifciations to manage it's view state and to whether it has child views visible or not.  i hope that makes sense.  i have a dB driven application so all view components are built and managed by there mediator, so going with a fresh start seems like it might be excessive when managing what view is displayed.

thanks all!