Page History

...

Related issue: The code above is actually representing the original 1.4 GetValues() call. So it might be wise, to put emphasis again on the still working 'pull approach', to introduce this a getValues() call, e.g.:

values = providingOutputItem.GetValues(consumerThatIsAsking);

This is considered to be a useful extension. It is a convenient method, and it explitly shows the pull approach, so we will add it .
( It might even be considered to move the method to the LinkableComponent (, see also Gena's suggestion on loop vs. pull later on this page).

1. Remark: When experimenting with the IsAvailable(), Rob B. and Stef introduced the IExchangeDefinition (see below). Rob K. actually introduced the same interface in the java version. Indeed it is quite natural entity, the exchange definition. Question: do we want to introduce it .

   Code Block
   java java
   public interface IExchangeDefinition { IValueDefinition ValueDefinition { get; } ITimeSet TimeSet { get; } IElementSet ElementSet { get; } }

...

1. Suggestion by Gena on pull / loop approach
   Discussion/Conclusion: / A good idea to introduce the GetValues, to recognize the pull approach. However, instead of on the LinkableComponent for now it has been put on the output item (see above).

...