Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
en:release_note_291 [2023/02/28 17:15] mashin created |
en:release_note_291 [2023/03/08 09:04] kkshin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)// | + | ===== Version 2.9.1 (V2.9.1.0) ===== |
| - | + | ==== Date ==== | |
| - | ===== 2.9.1 버전 (V2.9.1.0) ===== | + | 2023-02-23 |
| - | ==== 날짜 ==== | + | |
| - | 2023-2-6 | + | |
| \\ | \\ | ||
| Line 23: | Line 21: | ||
| * API [[BS2_QueryDeviceLicense]] has been added | * API [[BS2_QueryDeviceLicense]] has been added | ||
| - | <text size="x-large">2.</text> Added QR code recognition and authentication support feature using the camera. \\ | + | <text size="x-large">2.</text> Added features for QR code authentication by using the camera. \\ |
| * Refer to API [[configuration_api#BS2BarcodeConfig]] | * Refer to API [[configuration_api#BS2BarcodeConfig]] | ||
| - | <text size="x-large">3.</text> If an error occurs while reading and writing packets from the socket in the communication section, the SDK automatically retries a certain number of times. \\ | + | <text size="x-large">3.</text> Added retry count for communication used when an error occurs while reading or writing packets from the socket during communication. \\ |
| - | At this time, the number of retries was internally fixed and could not be changed. \\ | + | <callout type="warning" icon="true"> |
| - | As of the time SDK V2.9.1, it supports checking and changing the number of retries. \\ | + | **Warning** \\ |
| Increasing the number of retries is a way to resolve temporary errors, but care must be taken as direct causes such as network disconnection occurs, can lead to wasted resources by meaningless read/write retries when reconnection is required. \\ | Increasing the number of retries is a way to resolve temporary errors, but care must be taken as direct causes such as network disconnection occurs, can lead to wasted resources by meaningless read/write retries when reconnection is required. \\ | ||
| + | </callout> | ||
| * API [[BS2_GetSocketRetryCount]] has been added | * API [[BS2_GetSocketRetryCount]] has been added | ||
| Line 66: | Line 65: | ||
| ==== Modification function ==== | ==== Modification function ==== | ||
| - | <text size="x-large">1.</text> As with the keepalive check feature provided by the network switch, there are times when disconnection occurs after connection, even though it is not an actual device connection. \\ | + | <text size="x-large">1.</text> Fixed memory leak caused by network switches keepalive check being misunderstood by the SDK. \\ |
| - | Fixed a problem where the SDK could mistake this for an actual device connection and lead to a memory leak. \\ | + | |
| - | <text size="x-large">2.</text> The problem that occurred only in v2.8.3.2, which could lead to an abnormal shutdown was fixed while performing a log dump internally in the SDK when registering the user. \\ | + | <text size="x-large">2.</text> This is a problem that occurs only in ''version 2.8.3.2'', and a problem that can lead to abnormal termination during user registration while taking a log dump inside the SDK has been fixed. \\ |
| <text size="x-large">3.</text> Fixes were made to stabilize the code internally in the SDK. \\ | <text size="x-large">3.</text> Fixes were made to stabilize the code internally in the SDK. \\ | ||