
1) Add one more kind of prerequisite:
- persistent IOR
- name in Naming Service
- name for 2K Persistent Repository
- ServiceTypeName and constraints for Trading Service

2) Instead of hard-coding the event management inside a ComponentConfigurator
subclass, one could store the event management rules in a file that's read and 
interpreted at runtime. This would add one extra level of flexibility. One
would need to define this language that will be interpreted inside this
special type of ComponentConfigurator.

4) Use the CCM for event distribution instead of my current model.

5) For Future Work:
       - How to support fault-tolerance automatically without application
       participation or with minimal participation.
       - The same question with respect to replacement of components. Previous 
       research say it's not possible, is it true? To what extent?
