10-23-2018 04:12 PM
10-23-2018 05:06 PM
The way it works now is that any property designated as an interface property can be set by any session on that interface. This approach keeps it pretty simple in that you can set the interface properties first, last, once in the middle, or on every session. Interface properties are static so multiple writes to the same property will result in the last value being used. For example on the same interface, if session A is created and sets the baud rate to X before session B is created with baud rate Y, the interface will use baud rate B since it was called last.
It is my understanding that ease of use, flexibility, and a reduction of API complexity were the main drivers for these design decisions but that was before my time.