In the current prototype implementation of Charisma, the application composition is performed at link-time. However, this may be restrictive for applications that need component substitution at run-time. This limitation of Charisma can be removed by supporting dynamic loading of components at run time. Each component binary may be in the form of a shared object (``so'' in Unix, ``DLL'' on Windows). These components may be registered in a component repository that the application composer knows about. Component interfaces for registration, creation, and port-bindings could then be invoked by loading the component at runtime, and invoking appropriate functions in the loaded shared object by specifying their names. Also, we believe that dynamic loading will cleanly solve the namespace conflicts between components. This is crucial for increased reusability of components.