What is Linkar Framework .NET? |
The Linkar Framework Libraries allow the exchange of information with the server when they are included in compatible Projects.
They contain many functions that can be called from the application.
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 "Login" operation. Once the session is established, any operation can be executed without having to re-supply credentials.
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 conveniently manipulated. One of them also allows "Commands" to be executed (operations created using templates in XML or JSON format) across the Linkar Server.
Developers will find functions to execute operations, synchronously and asynchronously, in all these libraries. Functions that work in asynchronous mode instead of returning an object of type "string", return an object of type "Task <string>". Asynchronous functions run on a different thread than the main one, allowing the main thread not to wait until the end of the operation. 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.
Developers who want to create an application do not need to use all these libraries. They can just use the ones required for their purpose. The following section shows the hierarchy of the Linkar Framework libraries that will help them select the libraries needed in each case.