Isline Framework Series III--seven types of weapons

Take the above

Introduction to Isline FrameWork Provider

Among them Isline.data, Isline.applog is I want to focus on, but now first to talk about the role of each provider.

Dataprovider

Like other frameworks, Dataprovider provides the project with the ability to interact with the database, and its advantages are no longer articulated here, only to mention that it differs from the data access layer of other frameworks.

Dataprovider compatible with SQL Server and Oracle two databases, and open the Idboperater interface, users can provide an instance for Dataprovider by implementing the Idboperater interface factory, thus enabling the use of a third database Without having to modify the database call keyword. In addition, Dataprovider provides static access and instance access in two ways, for different ado.net containers, users can choose a different way, and provide a unified Dispose () method, the user only one call, you can turn off all the Reader , while a static call does not need to do any resource-release operations on it. Static access and instantiation access are distinguished by the way in which connection-oriented and connectionless work is done.

Dataprovider also provides users with Recordprovider, which allows users to easily manipulate. config files, text files, XML files, and so on.

Dataprovider comes with the data container option: ContainerDefiner.cs, using this class instance, the user can invoke various ADO objects directly, and the container to some large data objects for caching, compression, and other optimizations, these optimizations in storage to follow the "space for Time" Principle, in the transmission of "time for space" principle, the front desk business performance will be the essence of ascension!

Applogprovider

Applogprovider provides a powerful logging capability for users, who can provide separate configurations for each "log instance" in the program, each with a different "Render", and each Render representative can use a different "appender". The appender determines the important level of the log instance, recording media, record format, layout, and so on. All this user can be configured to complete without changing any code. In other words, if your original system log is all recorded in a text file and you now want to log it to a SQL or Oracle database, the only thing you need to do is change the configuration and if you have to output the log to the TV, you need to implement the Applogprovider distribution Iapplogprovider interface can be implemented.

If you have used log4net, then applogprovider you will be very familiar with, but Applogprovider provides a more flexible configuration.

Exceptionprocessprovider

Exceptionprocessprovider provides the user with the exception control function, it mainly divides into the abnormal record and the anomaly display two modules.

The exception recording module is based on Applogprovider, the user can pass exception instance to achieve the purpose of recording the exception, and Exceptionprocessprovider support user custom exception model, this model can be established with the whole software model, Through the entity Exception model (must inherit from Exception) to handle the event, and implement the Exceptionprocessprovider distributed interface, so as to achieve the function of abnormal recording. The abnormal display module refers to the notification information that is displayed to the user when the exception occurs, the form of these notices is divided into 10 kinds in Exceptionprocessprovider, the user can switch between these 10 styles only through the configuration.

Httpcontentprovider

Httpcontentprovider provides users with cookies, session, cache access methods, users through the configuration file, you can control the state of the amount of properties, such as cookie scope, sliding time, cache dependency mode (only SQL SERVER) and so on. By using these methods, users can easily establish, query, delete, and update these state quantities.

Islineframework

Islineframework is the core of the overall isline architecture, and before the architecture is loaded, IsLine.dll configures the entire architecture to complete the customization tasks.

Securityprovider

Securityprovider provides users with encryption and decryption, strong encryption and decryption methods. These encryption measures provide a basis for encrypting the password in the configuration file.

Taskqueueprovider

Taskqueueprovider is a service queue, users can use it to register existing services, Taskqueueprovider will be based on service node elements, return instances for users to use, thus building the enterprise application of the "field" model.

Fig. 3.3 Schematic diagram of project composition

The emphasis here is on Dataprovider and Applogprovider, because this paper has a large number of applications to these two provider.