Idea: Refactor AutomationFactory to be interface-based

[eoware]

By refactoring an interface out of AutomationFactory, alternate event handler paradigms could be implemented other than reflection-over-a-C#-assembly. An abstract factory pattern could be used so multiple paradigms could be used at the same time.

I am looking into building an asp.net web app that could use the current reflection factory as well as a javascript-parser that hooks up and executes script-based event handlers configured from a UI while also executing a set of standard handlers built in an assembly.