...
- Question: what does isAvailable() mean in case of multiple consumers. Do all consumers need to have the same time(s)?
- Leave in for now, review after more implementation, one suggestion of modification bool isAvailable(whosAsking);
Will be discussed later during the meeting, Stef will show an example of using isAvailable(whosAsking); #OpenMIException : Exception. However, first we will have a detailed look at the guidelines for introducing custom exceptions in both .Net and Java. Rob K. has added a page for this, Guidelines for introducing custom exceptions. It now includes Java suggestions, Gena will add .Net suggestions.
3.5 More suggestions on v2.0 changes
- Move IsAvailable to IExchangeItem. Is it only for a thread-safety? If yes than see also ICollection.IsSynchronized
Stef: The question is confusing, the actual issue is that we should distinguish between IsAvailable and IsValid.
We are now realized that there is a difference between IsAvailable (only for output item, means it is for consumers) IsValid (probably for IExchangeItem, meaning if item is valid in the context of current component, maybe updated during Validate() call)? - Move Values { get; set; } to IExchangeItem?
- get; set; to be reviewed at this meeting
: Discuss component operation mode hereWhen discussing get/set, the subject of the discussion graduallly moved to the pull versus loop driven approach. This led to an important decision
: We will introduce a boolean argument that indicates whether the component should run in a pull mode (like in OpenMI 1.4) or in loop mode
Wiki Markup Add *params* keyword to IArguments\[\] args parameter in Initialize(IArgument\[\] args).
- Adrian review, if happy then ...
- Adrian review, if happy then ...
- "string Validate()" / "bool IsValid(IExchangeItem item)" / "IsAvailable()", etc.
- to be reviewed at this meeting
Wiki Markup (y) Add "params IOutputItem\[\] items" argument to Update() in order to specify explicitly what should be updated.
- Maybe generalise to IExchangeItem i.e. allow IInputItem?
- Remove AddConsumer/RemoveConsumer and use BindingList in the implementation instead to listen to IOutputItem.Consumer.Add() / Remove()
We will leave AddConsumer/RemoveConsumer for now. The BindingList mechanism has been implemented, though, so anyone can use it
- When we get loops in the compositions - we have to tell which component will be first! In the new GUI, we will let the user indicate the 'Start up component'.
...