Next: References
Up: Conclusions
Previous: Breakeven Point of Adaptation
The current implementation of
the repository has the drawback
that instances of all implementation classes
must be hold in the memory
in order to get the according implementation profiles.
This is sufficient if only a small
number of implementation classes
are needed as in the case of the sample application.
Since a strength of dynamic adaptation
is the gain of bandwidth in the case of
a high number of implementation classes
with a big size,
the repository of the current implementation
may become a bottleneck.
The solution may be the loading
and instantiating of each implementation
class at start-up time of the repository.
After the startup the separated profiles are saved only.
A further improvement concerning
transparency would be the
implementation of an adaptor generator
which generates Java byte code during runtime
and not Java source code as
in the prototype implementation.
Copyright Munich Network Management Team