I'm building a framework where the user creates a configuration file that defines how the Flex application is constructed. One part of this framework allows the user to define a data visualization along with the components used in the construction. Now I'm adding the ability to define and add filter logic so that once the visualization is created, it can be filtered dynamically at run-time. I currently build the visualization from the configuration file and create/register mediators for the view components when the application starts. For the filtering, I was thinking I could encapsulate the logic and functionality in a separate mediator that would point to a view that is already being mediated. This would allow me to have one mediator manipulate the view's regular state, events, etc and then have another mediator handle the filtering notifications being applied. Obviously, I could use one mediator to do both tasks but this means that my existing mediators have to be made even more complex with the addition of filtering behavior methods, etc.
So, does it make any sense to try to use more than one mediator for a single view if the functions being handled by each mediator on that view are clearly defined?