transport

All outputs which use the freq attribute should understand period as an alias which makes it more consistent for instance with flow definitions and also unit wise it is in fact not a frequency

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

Whilst looking at #1352 i noticed a refactoring opportunity a big amount of callers of Audio::playSound are wasting time calculating a value that is never used.
The problem is with void playSound(SoundId id, const Map::Pos3& loc, int32_t pan); this function should ONLY be used by the audio hooks. Never by code we are writing. This is because we have `void playSound(SoundId id, const Map::Po

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.

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

Will speed up install times, could lead to future depreciation.