You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Acuant JavaScript Web SDK v11.9.0
1
+
# Acuant JavaScript Web SDK v11.9.1
2
2
3
3
**July 2023**
4
4
@@ -191,7 +191,7 @@ The SDK includes the following modules:
191
191
PREVIEW: https://preview.acas.acuant.net
192
192
```
193
193
194
-
1. After *initialize* or *initializeWithToken* succeeds, start the Web Workers. By default, the function *start* starts all the Workers. Alternatively, you can provide a boolean to enable the single worker model. The single worker model will only start one worker at a time and is intened for low-end devices which struggle to run both workers at the same time. Be aware that this model might degrade the overall performance.
194
+
1. After the *initialize* or *initializeWithToken* function succeeds, start the Web Workers. By default, the *start* function starts all the Workers. Alternatively, you can provide a boolean to enable the single worker model. The single worker model starts only one worker at a time and is intended for low-end devices that struggle to run both workers at the same time. Note that this model might degrade the overall performance.
195
195
196
196
```js
197
197
AcuantJavascriptWebSdk.start(
@@ -797,14 +797,7 @@ See the [WebView ReadMe](docs/WebViewReadMe.md) for documentation on WebViews.
797
797
798
798
## Improved support for devices with extreme memory constraints
799
799
800
-
Although the Web Workers use only a minimal amount of memory, you can reduce the memory usage by running only one of the Web Workers at a time. This is recommended only if you have severe memory constraints that you can not address any other way. Normally when both **AcauntImageWorker** and **AcuantMetricsWorker** are running simultaneously, they seamlessly make calls between themselves until they are ready to return a finished image that has been cropped and has had all the metrics run on it. If only one is running at a time, the workflow has to look like this:
801
-
802
-
- AcuantImageWorker is started to perform detect in your custom camera implementation
803
-
- AcuantImageWorker is ended and AcuantMetricsWorker is started to perform moire on the uncropped image
804
-
- AcuantMetricsWorker is ended and AcuantImageWorker is started to crop the image
805
-
- AcuantImageWorker is ended and AcuantMetricsWorker is started to perform the remaining metrics on the cropped image
806
-
807
-
Starting and stopping Workers is a very slow operation, so you will see performance losses with this approach. Therefore, use this approach only if absolutely necessary. See [Reference of AcuantJavascriptWebSdk methods](#reference-of-acuantjavascriptwebsdk-methods) for more information about the methods.
800
+
See the single worker model in [Initialize and Start the SDK](#initialize-and-start-the-sdk).
0 commit comments