search

SamCooper / COMMON_SPEC_RIDS

1 stars 0 forks source link

[Configuration service] Should we emit a ConfigurationSwitched event when we initially configure the configured service using getCurrent? #114

Closed apinder closed 5 years ago

apinder commented 5 years ago

3.4.9.1 states:

"The [getCurrent] operation can also be used to determine the initial configuration of a service provider before it has been activated, it is therefore a useful operation to call by a service provider during start-up to determine its initial configuration."

The configured prototype initialises itself with the getCurrent operation - as above - in terms of the Configured service this is a switch of configuration but it is not triggered by an activate interaction - should we emit a ConfigurationSwitched event in this case or not?

This might be out of scope and implementation specific so feel free to ignore.

lacourte commented 5 years ago

I would say no, but it seems it is not explicitely forbidden so it should be possible. I hope my tests will handle that properly if you do.

apinder commented 5 years ago

Agree, clarified in the spec that we should not emit a switched event if this is the case