|
|
Post by scottbusi on Jun 16, 2021 15:58:27 GMT
For NTPServers is there a limit of how many can be supported and is it located in one of the specs? I have been unable to find documentation on this
On this vendors server I get the following when I try to patch 3 NTPServers
{"@odata.type":"#Message.v1_0_8.Message","Message":"Maximum 2 NTP Servers can be configured. The value for the given property exceeds the maximum allowed value.
|
|
|
|
Post by mraineri on Jun 17, 2021 12:17:16 GMT
There is no standard limit since ultimately this is determined based on the implementation's architecture. Services can convey their limit though by null padding the property. The following statement is found in the "Array properties" clause:
So, if a service only supports two NTP servers, and only one is configured at this time, I would expect the service to show this as the NTPServers property:
"NTPServers": [
"ntp.contoso.com",
null
]
|
|
|
|
Post by michaeldu on Jun 30, 2021 7:43:07 GMT
What does the "restrictive maximum size" mean? In the spec, it mentioned "Services should not pad array properties if the maximum array size is not restrictive. For example, an array property typically populated with two elements, that a service limits to a maximum of 16 elements, should not pad the array with 14 null elements." For this case, why can't we pad null for the array?
|
|
|
|
Post by mraineri on Jul 1, 2021 13:03:40 GMT
It adds extra cruft to the payload; ultimately you can still pad it (it's a "should" as opposed to a "shall"), but it's generally not needed when the array is sufficiently large and you don't expect the client to ever consume all of the array slots.
So, taking the NTP servers example, if you support up to 16 NTP servers, is it realistic for the client to configure 16 different NTP servers? Probably not.
|
|
