unetjs 4.0.2 → 5.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/cjs/unet.cjs +1171 -774
- package/dist/esm/unet.js +1171 -774
- package/dist/unetjs.js +1170 -773
- package/dist/unetjs.js.map +1 -1
- package/dist/unetjs.min.js +1 -1
- package/dist/unetjs.min.js.map +1 -1
- package/package.json +8 -8
package/README.md
CHANGED
|
@@ -77,6 +77,8 @@ UnetSocket API acheives this using two mechanism, firstly, it can request ALL of
|
|
|
77
77
|
|
|
78
78
|
Secondly, the UnetSocket API caches the responses to parameter requests for a limited time. If the user requests the same parameter again, the UnetSocket will return the cached response. The time to cache a response is set by the `cacheTime` property in the `CachingAgentID` constructor.
|
|
79
79
|
|
|
80
|
+
> unetsockets.js v5.0.0 and beyond the UnetSocket API was changed to remove the optional parameter `caching` from the `agentForService`, `agentsForService` and `agent` methods. This was done to simplify the API and avoid confusion. The caching behaviour is now enabled by using a different class, `CachingGateway` instead of `Gateway`. The `CachingGateway` class extends the `Gateway` class and adds the caching behaviour.
|
|
81
|
+
|
|
80
82
|
```js
|
|
81
83
|
import {UnetMessages, CachingGateway} from 'unetjs'
|
|
82
84
|
let gw = new CachingGateway({...});
|