A configurable polling interval (default: 30 seconds) is used between series of requests. Requesting about 15 parameters takes just one or two seconds, so the remainder of the time between polling is available for data updates to the Studer servers.
So far I haven’t seen any interference with Studer portal communications yet.
But in case users request a higher number of parameters, taking more time to do those requests, that interference might occur.
So it might be better to divide the requests into smaller bursts, so request 5 or 10 values, then wait for a second and do the next 5 or 10.
After all parameters have been requested in these bursts, the integration will then wait for the next polling interval.
A configurable polling interval (default: 30 seconds) is used between series of requests. Requesting about 15 parameters takes just one or two seconds, so the remainder of the time between polling is available for data updates to the Studer servers. So far I haven’t seen any interference with Studer portal communications yet.
But in case users request a higher number of parameters, taking more time to do those requests, that interference might occur. So it might be better to divide the requests into smaller bursts, so request 5 or 10 values, then wait for a second and do the next 5 or 10. After all parameters have been requested in these bursts, the integration will then wait for the next polling interval.