Post by tophercantrell on Oct 30, 2018 13:13:50 GMT
I may be mistaken here (I am still a noob and learning), but Redfish arrays are fixed length, right? The client cannot patch back a shorter or longer list for the array. For true lists that grow/shrink I would use a collection, right?
If my implementation of EthernetInterface.StaticNameServers supports two entries, then back and forth I would always send two entries.
Most other arrays have two types: the "real" type and "null" to use for "empty slots".
If this were the case for EthernetInterface.StaticNameServers then we could use entries like ["1.2.3.4",null] and [null,"1.2.3.4"] and [null,null].
Since "null" is not an option, should we use an empty string like ["1.2.3.4",""] and ["","1.2.3.4"] and ["",""] ?
If my implementation of EthernetInterface.StaticNameServers supports two entries, then back and forth I would always send two entries.
Most other arrays have two types: the "real" type and "null" to use for "empty slots".
If this were the case for EthernetInterface.StaticNameServers then we could use entries like ["1.2.3.4",null] and [null,"1.2.3.4"] and [null,null].
Since "null" is not an option, should we use an empty string like ["1.2.3.4",""] and ["","1.2.3.4"] and ["",""] ?
