Hi,

For safety use, it's better to have null check for all variables which are used in this function.

if (!_sessionPriv.$clientAlarmList) {
    return;
}

↓

if (!_sessionPriv.$clientAlarmList
     || !_sessionPriv.$monitoredItemForAlarmList
     || !_sessionPriv.$subscriptionforAlarmList ) {
    return;
}

https://github.com/node-opcua/node-opcua/blob/master/pack

Since the content is different and they have different schemas, they should also have different root elements, although this might break scripts for some people. We should of course accept the old version as well. Comments are welcome!

When adding multiple rpc target classes, if multiple targets contain the same\similar method, the method in first target added is used (as documented). But I miss an option to disallow duplicates, as this is (in my case) always an error. Alternatives:
-Preferably a setting on JsonRpc itself that produce error when AddLocalRpcTarget is called
-A setting on JsonRpc itself that produce error during

Story

As a client

I want to use exp back-off and randomisation on retries

So that I prevent the "thundering herd" problem and avoid DDOSing the server when it restarts

Acceptance criteria

• Client uses the exp back-off for retries
• Client randomises the initial timeout on retries

The documentation can be added to: https://napalm-logs.com/en/latest/syslog/index.html - help would be greatly appreciated.