Clarification about changing variables org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip

[paulfilip]

The standard implies that In the case the XCP service is not multi-session capable and both of the variables org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip are set to true, the FMU must return an error in the corresponding setter function and provide a meaningful error message.
I think that the way variables are changed in Configuration Mode matters in this case.
For example, if by default the XCP is enabled on TCP and disabled on UDP and the user wants to make it vice versa, then one could

1. set EnableXcpOnUdpIp to true
2. set EnableXcpOnTcpIp to false

Although the final state is a valid one (only one of TCP/UDP is active), the intermediate state (when both variables are true) will cause the FMU to return with an error. A solution in this case is to reverse the commands 1 and 2 from above.
Would it be beneficial if this check will be performed later (e.g in exitConfigurationMode if the FMU does not support both protocols in parallel)?