Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Question: what does isAvailable() mean in case of multiple consumers. Do all consumers need to have the same time(s)?
    1. Leave in for now, review after more implementation, one suggestion of modification bool isAvailable(whosAsking);
    2. (warning) (question) Will be discussed later during the meeting, Stef will show an example of using isAvailable(whosAsking);
    3. "string Validate()" / "bool IsValid(IExchangeItem item)" / "IsAvailable()", etc.
    4. (question) to be reviewed at this meeting

Related issue: The code:

Code Block
java
java
while (!providingOutputItem.IsAvailable(consumerThatIsAsking)) {
    providingOutputItem.Component.Update(providingOutputItem);
}
values = providingOutputItem.Values;

...

Discussion/Conclusion part 2: (thumbs up) We decided to let the LinkableComponent have a propery: CascadingCallsDisabled.
The default is false, indicating that the component is running in Pull Driven mode (there will be a cascade of update() calls. This Pull Driven mode has to be supported by every component.
If set to true, the component is expected to run Update()-step by Update-Step(), controlled by some outer world (which may be another component). If the component does not support this Update() by Update() way of running, it will throw an Exception when CascadingCallsDisabled = true is called;

  1. "string Validate()" / "bool IsValid(IExchangeItem item)" / "IsAvailable()", etc.
    • (warning) to be reviewed at this meeting
  1. The Timezone issue has to be re-adressed. According to Adrian it is not doing what we expected.

...

  • Decorator issues, GUI:
    • How to support the end user, when "chaining" decorators? (thumbs up) Taken care of, see section 2.5
  • Decorator issues, other:
    • (question) Is is useful to let the component have a property OutputDecorators, containing the list of already created decorators?

...