Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
en:possible_integration_options_3_in_biostar_2 [2020/04/16 13:40]
yjjung [How G-SDK works?] 		en:possible_integration_options_3_in_biostar_2 [2025/08/20 10:03] (current)
mwkim
Line 1: Line 1:
 ==== Possible Integration Option 3 : G-SDK ====  ==== Possible Integration Option 3 : G-SDK ==== 
 \\ \\
-In addition to the integration method using BioStar2 API or BioStar2 Device SDK, G-SDK has been released as a new integration option. \\+In addition to the integration method using BioStar2 ​SW API or BioStar2 Device SDK, G-SDK is recently ​released as a new integration option ​for device management, user management, and log management. \\
  
 ==== What is G-SDK? ==== ==== What is G-SDK? ====
 G-SDK is one of the integration options for communicating with BioStar 2 devices. It is a lightweight,​ scalable, and cross-platform solution which will expedite your development. \\  G-SDK is one of the integration options for communicating with BioStar 2 devices. It is a lightweight,​ scalable, and cross-platform solution which will expedite your development. \\ 
-Based on gRPC, it supports many programming languages such as Java, C#, Python, Node.js, Go, etc. \\  
 \\ \\
  
 ==== How G-SDK works? ==== ==== How G-SDK works? ====
-{{:​en:​gsdk_gsdkarchitecture.png?​600|}} \\+{{:​en:​gsdk_gsdkarchitecture.png?​550|}} \\
 ** [Figure 1. G-SDK architecture] ** \\  ** [Figure 1. G-SDK architecture] ** \\ 
 \\ \\
Line 16: Line 15:
 (gRPC (gRPC Remote Procedure Calls) is an open source remote procedure call (RPC) system initially developed at Google in 2015.) \\ (gRPC (gRPC Remote Procedure Calls) is an open source remote procedure call (RPC) system initially developed at Google in 2015.) \\
 \\ \\
- 
- 
 ** Multi-language support ** ** Multi-language support **
   * Language-neutral IDL   * Language-neutral IDL
   * Native client libraries   * Native client libraries
-\\ 
 \\ \\
 ** Device Gateway ** that communicates with BioStar 2 device can be run on a server or cloud. ** Core modules ** use BioStar 2 protocols and written by GO language.\\ ** Device Gateway ** that communicates with BioStar 2 device can be run on a server or cloud. ** Core modules ** use BioStar 2 protocols and written by GO language.\\
Line 30: Line 26:
  
 ==== What is different from BioStar 2 Device SDK? ==== ==== What is different from BioStar 2 Device SDK? ====
-Existing BioStar 2 Device SDK provides C++ library with C#. G-SDK is released to provide flexible development for those who would like to meet the requirements below. ​+Existing BioStar 2 Device SDK provides ​<​nowiki>​C++</​nowiki> ​library with C#. G-SDK is released to provide flexible development for those who would like to meet the requirements below. ​
  
 Let's take a look for an easy comparison between BioStar 2 Device SDK and G-SDK. \\ Let's take a look for an easy comparison between BioStar 2 Device SDK and G-SDK. \\
Line 37: Line 33:
 \\ \\
 \\ \\
-One of the biggest advantages of G-SDK compare to Device SDK is that it supports various languages. For the last years, Device SDK users have had difficulty using development language other than C++ or C# which is in the sample code. \\ +One of the biggest advantages of G-SDK compare to Device SDK is that it supports various languages. For the last years, Device SDK users have had difficulty using development language other than <​nowiki>​C++</​nowiki> ​or C# which is in the sample code. \\ 
-Since BioStar 2 Device SDK can communicate with C++ library, you have to use C++ language or need to marshall all the APIs and structures in the library into other languages. Currently BioStar 2 Device SDK provides only C# marshalling sample. \\+Since BioStar 2 Device SDK can communicate with <​nowiki>​C++</​nowiki> ​library, you have to use <​nowiki>​C++</​nowiki> ​language or need to marshall all the APIs and structures in the library into other languages. Currently BioStar 2 Device SDK provides only C# marshalling sample. \\
 This is a limitation of BioStar 2 Device SDK due to the structure. \\ This is a limitation of BioStar 2 Device SDK due to the structure. \\
 {{:​en:​gsdk_devicesdkstructure.png?​900|}} \\ {{:​en:​gsdk_devicesdkstructure.png?​900|}} \\
Line 78: Line 74:
 ** Supported OS ** \\ ** Supported OS ** \\
 Windows, x86/Arm Linux, Mac OS \\ Windows, x86/Arm Linux, Mac OS \\
 +\\
 +** Recommended Requirements **\\
 +2.0GHz CPU, 4GB(32bit) or 8GB(64bit) RAM  \\
 +\\
 +** Minimum Requirements **\\
 + ​1.0GHz CPU, 1GB(32bit) or 2GB(64bit) RAM\\
 +\\
 ** Maximum number of devices ** \\ ** Maximum number of devices ** \\
 Up to 1,000 \\ Up to 1,000 \\
 +\\
 ** Supported Language ** \\ ** Supported Language ** \\
-C++, Java, Python, Go, Ruby, C#, Node.js, Android Java, Objective-C,​ PHP, Web \\+<​nowiki>​C++</​nowiki>​, Java, Python, Go, Ruby, C#, Node.js, Android Java, Objective-C,​ PHP, Web \\ 
 +\\
 ** Supported API ** \\ ** Supported API ** \\
 The basic AC APIs(Access control, User management, Event log etc) except advanced features such as Zone, Wiegand, RS485 features. \\ The basic AC APIs(Access control, User management, Event log etc) except advanced features such as Zone, Wiegand, RS485 features. \\
 +\\
 ** Supported Device ** \\ ** Supported Device ** \\
 All BioStar 2 devices \\ All BioStar 2 devices \\
-\\ 
-** Not Supported Device ** \\ 
-All BioStar 1 Devices \\ 
-(BioEntry Plus v2, BioEntry W v2, XPass v2, XPS2 v2, and BLN v2 are not supported.Gen 1 devices are not supported) ​ \\ 
 \\ \\
 ** Download ** \\ ** Download ** \\
-https://​github.com/​biostar-dev/​g-sdk/​ \\+https://​github.com/​biostar-dev/​g-sdk/​releases ​\\
 \\ \\
 ** Manual ** \\ ** Manual ** \\
Line 98: Line 100:
 \\ \\
 \\ \\
- 
-