Re: Mini meeting Toulouse 22-23 april / Execution Engine

On Thu, 18 Apr 2002, Christian Schlegel wrote:

[...]
> What I think is important to consider is that there are several ways of
> organizing the internal strucuture of a component despite the use of a
> particular "execution engine". 

I don't understand what you mean with ``despite the use of''...

> For example, the state mechanism provided
> by the "SmartConfiguration" class has also been used successfully in
> three layer architectures with a task net execution mechanism on top of
> the various components. That state mechanism works different to the Genom
> approach and I think both have their particular strengths and weaknesses.

What I would like to come to is a further decomposition of the Genom
work into a pure sequencing library (that can indeed be used
``everywhere'', independent of the task) and task-dependent libraries
that implement the functionality. So, I think this is also what you
are trying to do (implicitly)?

> The key with respect to configuration has been the fact that one can
> abort blocking communication calls if one wants to enforce a component to
> reach a particular state. Therefore I am always pointing out that there
> is a relationship between the state change mechanism and the
> communication patterns.

Indeed. This observation holds for _all_ activities in the system, so
that's why it's useful to have a library dedicated to it.

Herman