bNesis.Sdk.ThinClient 1.8.13

bNesis SDK for C# (.NET)

Introduction

bNesis SDK for C# (.NET) allows developers easily use cloud services authorization and API in .NET applications developed in C# programing language.

Comfortable service programming with bNesis SDK

The authorization is most common challenge of cloud services programing because complexity of OAuth 2.0 protocol and OpenID identity layer. Also network programing required havening wide range of tech knowledge. The bNesis SDK represented all of it as simple well-known program elements and it makes coding process easier and more intuitive. Code examples demonstrated how to use the bNesis SDK for C# (.NET) for connection of cloud services in .NET applications and relevant guides are also provided. Any changes and updates of cloud services APIs are handled by versions of bNesis SDK for C# (.NET). bNesis SDK for C# (.NET) significantly reduces coding time and project expenses.

bNesis API layers

bNesis SDK APIs provide an wrappers over the "low-level" of services APIs - also known as bNesis SDK API layers. There are three layers:

• Unified API. At this layer bNesis SDK APIs return to developer the response as complete data structure with fields corresponding to the original service response fields. Developer operates with data structures in the C# programming language. Universal data structures for similar API groups are used for similar services. Unified API is used by developers for implementing cross-service solutions, when the same program code, without changes, has to work with different services.

• Formalized API. At this layer bNesis SDK APIs return to developer the response as complete data structure with fields corresponding to the original service response fields. Developer operates with data structures in the C# programming language. Of course, formalized API is very effective when complex data structure is waited as response.

• Raw API. By using this layer of bNesis SDK APIs, developer obtain full response from service including all fields and status codes which is provided by service owners. There are two reasons for supporting API of raw layer. The first is then there is code working properly with connected service and developer want to start using of bNesis SDK. In this case developer can save his code of service responses processing i.e adopting of exiting code to bNesis SDK does not need global changes. The second is a complete correspondence of the original documentation to the service. It is not usual and not informative but there can can be and vice versa. By the way, often responses with errors contain detailed descriptions which is useful for debug mode.

Providing Rich and Thin clients architecture

Planing of using cloud services in .NET applications system designer determines optimal architecture depending on whether lengthy computations must be accomplished by the client or the server. bNesis SDK for C# (.NET) provides an opportunity to realize these two modes - Rich client mode and Thin client mode. At the API level, functional of Thin client mode is fully compatible with Rich client mode, the only difference is that in the case of Thin client, the OAUTH authorization takes place on the side and in the context of bNesis API Server.

Rich client mode. In this case, bNesis SDK is delivered as a library for .NET and all the accesses to cloud services are direct:

• Middleware server is not used.
• OAUTH authentication is performed on the side of your application;
• Multiple applications can use one installed bNesis SDK library.
• NuGet install packages and version control support is provided.
• Handlers for different services are stored in separate libraries, so you can control the size of bNesis SDK package, depending on the number of services your application uses.

Advantages: ability to use multiple applications, independence from intermediate servers.

Thin client mode. In this case, bNesis SDK is delivered as a library for .NET and works with cloud services through bNesis API Server provided as the server software:

• At the API level, functional of Thin client is fully compatible with Rich client, the only difference is that in the case of Thin client, the OAUTH authorization takes place on the side and in the context of bNesis API Server. In particular, it allows you to distribute OAUTH authorization for a single account across multiple workstations.
• NuGet install packages and version control support is provided.
• In the case of changes in the cloud services API, you don't need to update your application.
• bNesis SDK Thin client is completely a cross-platform and multi-lingual solution. In this case, all the functionality is moved to bNesis API Server, only RESTful API interface is on the client side.

Advantages: small size, cross-platform, authorization distribution.

Contacts

For public https://bnesis.com

For developers https://api.bnesis.com