DONE
====
- present 1.4 right at the beginning of section 1.

- Smalltalk component model? OpenDoc? GNUstep (OpenStep)? 

- talk more about reflective systems. How my model could be implemented using
a reflective system. Why am I not using it. Also aspect-oriented programming.


- synchronization: left to the developer. Is there anything I can do to
automate it? May I just write that I will investigate it. Or not, I think that I 
already provide the support: events, etc. What I need to do is to instruct my
developer about how to do it. Use \dTAO as an example.

- How to prove my thesis: 
   a) present a theoretical model
   b) present an implementation of the model
   c) deploy the implementation in 2 applications to support different kinds
   of automatic configuration:
       1) modify the topology of the reflector network to deal with
       fault-tolerance.
       2) customize the reflector code by dynamic linking the appropriate
       modules on demand based on the protocols the reflector will need.
       3) support safe reconfiguration of \dTAO. In this case, the
       reconfiguration is triggered by an external entity (system administrator,
       application, or adaptation module) but the ComponentConfigurator
       architecture guarantees that the reconfiguration process is carried out 
       safely taking care of synchronization issues.

- move list of futurelly-implemented TAO strategies out of completed work.

- mention "WYNIWYG (see section \ref{sec:dependence})" in the description of
the reflector experiment. Make sure that the last 3 itens of the thesis
(examples of automatic reconfig) are well covered before. Look at the
description of the 3 items in this file and update the prelim.tex file.

- print, read, and give it to Roy.

TODO
====



