Linkar FRAMEWORK is a set of open-source libraries that allows developers to create their own applications that connect to the linked Linkar Server to access the different MV Databases.
Linkar FRAMEWORK is made up of a total of 15 libraries. 14 of them are open source. Only one is private and delivered compiled. This private library basically has two functions; one is to execute Persistent operations and the other to execute Direct operations:
•Persistent operations require a session to be established and closed through “Login” and “Logout” operations. The connection credentials to Linkar Server are supplied in the "Log-in" operation. Once the session is established, any operation can be executed without having to re-supply credentials.
Note: The Linkar Framework Persistent functions should not be used if multiple redundant containers are running behind a load balancer. The Login function will generate a client session in the container that the load balancer decides, and subsequent requests made with the same client session may be re-routed to other containers.
•Direct operations do not require a session to be established. The connection credentials must always be supplied to the Linkar Server with each operation.
These two "primitive" functions, allow developers to create CRUD applications and call MV Basic subroutines across the Linkar Server. Developing an application with just these two primitives would be very difficult and time expensive.
The other 14 libraries are open-source. Developers can always design their own new custom libraries in two different ways:
•Relying on open source libraries, and designing a new one from them.
•Modifying the open-source libraries to adapt them to the specific needs of their application.
These libraries provide functions that allow the MV type input and output buffers to be con-veniently manipulated. One of them also allows "Commands" to be executed (operations cre-ated using templates in XML or JSON format) across the Linkar Server.
These libraries help developers to create applications faster. Some of them are based on the two primitive ones. For example, there are libraries that allow operations with input and output data in XML or JSON format. There are also libraries that allow you to work with input and output data in a very similar format to an MV buffer.
Developers will find functions to synchronously and asynchronously execute operations, in all these libraries. Functions that work in asynchronous mode instead of returning an object of the "string" type, return an object of "Task <string>" type. Asynchronous functions run on a different thread than the main one, allowing the main thread not have to wait until the end of the operation. (not in C Library)
Developers who want to create an application do not need to use all these libraries. They can use only the needed ones for their purpose. The following section shows the hierarchy of the Linkar FRAMEWORK libraries that will help them to select the needed libraries in each case.
Linkar FRAMEWORK is available with different programming languages and environments:
•The .NET Framework libraries are for Windows x64 and x86 environments, and languages including C#, Visual Basic, and F#.
•The .NET Core libraries are for multi-platform development including Windows, Linux, and macOS with C#.
•Java is for all OS types.
•The C Library can be used with all languages and environments, including within PHP, Python, and Node.js.
•The Node.js and Python Framework libraries for easily building fast and scalable network applications.
The following languages and environments are available in the version of Linkar CLIENTS. They will soon be adapted to Linkar FRAMEWORK:
•The COM Library found in the .NET Framework package.
•The Mono Library
•The PHP extension.
