CN105302575A - Foundational development framework - Google Patents

Abstract

The invention relates to a basic development framework. The basic development framework is developed by using C#, HTML, CSS and Javascript languages, including: UI interface display layer, service control layer, entity storage layer, authority control layer, log management layer and tool assembly ; UI interface display layer, authority control layer, service control layer and entity storage layer are connected sequentially; UI interface display layer realizes cross-platform application development through components composed of HTML, CSS and JavaScript, and is suitable for Web applications with B/S structure The interface development of the program; the service control layer, the entity storage layer, the authority control layer, the log management layer and the tool assembly are all based on Microsoft.NET Framework 4.0 and written in C# language. The beneficial effects of the present invention are: adopting the operating mechanism of the independent program domain, and implementing a program execution pool, the creation, update, and destruction of all independent program domains are managed in a unified manner, and at the same time, combined with the authority control interface and the log production interface for monitoring. It provides a means for the execution control of business classes.

Description

A basic development framework

technical field

The invention belongs to a development framework, and in particular relates to a basic development framework.

Background technique

Most of the common development frameworks in the market are basically facing the problem of a certain link in the application development process, and the pertinence will be strong. It is difficult to effectively and seamlessly connect the technologies of each link, and this also greatly increases the learning cost and maintenance cost of the enterprise.

In the process of enterprise application development, due to the lack of professional program developers, companies usually adopt the method of cooperating with IT service companies for program development. Due to the technology accumulation and personnel skills of the IT company itself, the technical means and implementation methods of enterprise application development are often diversified, which increases the technical risks, learning costs, and maintenance costs of enterprise applications. However, due to the asymmetry of technology and professionals, the enterprise itself cannot fundamentally solve this problem.

Contents of the invention

In order to solve the above-mentioned problems in the prior art, the present invention provides a development framework. The basic structure of the invention can meet the two modes of B/S client and C/S client, uniformly use a service processing layer at the server end, and use a unified communication protocol. Therefore, the B/S client and C/S client of one or more applications can be supported on one server side at the same time.

The technical scheme adopted in the present invention is:

A basic development framework, which is improved in that: the basic development framework is developed using C#, HTML, CSS and Javascript languages, including: UI interface display layer, service control layer, entity storage layer, authority control layer, log management layer and tool assemblies;

The UI interface display layer, the authority control layer, the service control layer and the entity storage layer are sequentially connected;

The UI interface display layer realizes cross-platform application development through components composed of HTML, CSS and JavaScript, and is suitable for interface development of Web application programs with B/S structure;

The service control layer, entity storage layer, authority control layer, log management layer and tool assembly are all based on Microsoft.NETFramework4.0 and written in C# language.

Preferably, the UI interface is based on the self-developed JavascriptUI framework, and the UI interface components include text components, drop-down selection components, group check/radio components, list components and menu components; the UI interface components can be freely combined to form New components, including basic components, composite components and business components;

The basic component is a minimum functional component, which is used to realize the smallest unit;

The composite component is composed of more than two basic components, and is used to realize the interaction of the smallest unit;

The business component is composed of two or more basic components or composite components, and is used to minimize the association with direct business functions.

Preferably, the service control layer enables relatively isolated operation between the service and the main program, and between the service and the service, and at the same time introduces service version management, so that the service can be upgraded or downgraded without stopping the service; the service control layer specifically Apply methods include creating executors, executing calls, and unloading executors.

Further, the creating executor includes (1), starting to create; (2), creating an application domain; (3), loading a public assembly; (4), judging whether the loading is successful; (5), loading a private program (6), judging whether the loading is successful; (7), if successful, the creation is completed; wherein, if the loading fails in steps (4) and (6), an exception message will be thrown to the caller.

Further, the execution call includes (1), start calling; (2), create a call information object; (3), use the executor to execute the call; (4), determine whether the call is successful; (5), return call execution Result; (6), the call is completed; wherein, if the call fails in step (4), an exception message is thrown to the caller.

Further, the uninstallation executor includes (1), start uninstallation; (2), obtain the application domain; (3) judge whether the program can be uninstalled; (5), uninstall the application domain; (6) complete the uninstallation; If uninstallation fails in step (3), an exception message will be thrown to the caller.

Preferably, the entity storage layer includes a database connection pool, a SQLHelp help class, an outer packaging class, and a SQLXML reading and management help class;

The database connection pool is used for data persistence operations, which include creating data connections, releasing data connections, statement execution and operations related to data persistence;

The SQLHelp helper class supports SQL variable replacement and insertion, SQL transactions, multiple database types, independent storage of SQL text, and ORM object storage of Microsoft Entity Model;

The outer encapsulation class supports SQL variable replacement and insertion, SQL transactions and various database types.

Preferably, the authority control layer includes a function point management module, a role management module, a role authority management module, and a role personnel management module; the authority control layer adopts an interface design for accessing third-party personnel information and SSO control information.

Preferably, the log management layer includes system logs, business logs and user logs;

The system log is used to integrate in the service control layer, entity storage layer and authority control layer, and automatically record all call log information;

The business log is used to integrate in the service control system and record all business data log information by itself;

The user log is used for external release in the form of an open interface, and the developer calls and records relevant log information in the program code according to his own needs.

Preferably, the tool program set includes a character processing program set, an image processing program set, a serialization program processing set, an encryption and decryption program processing set, and a compression and decompression program processing set.

The beneficial effects of the present invention are:

The present invention adopts an independent program domain operating mechanism: this function realizes the isolation of business classes and infrastructure classes, and creates a sandbox-like operating environment for business classes. In the infrastructure, we implement a program execution pool to manage the creation, update, and destruction of all independent program domains in a unified manner, and monitor them in conjunction with the authority control interface and log production interface. It provides a means for the execution control of business classes. Including: 1. Isolation of infrastructure programs and business programs; 2. Standard and unified call interface; 3. All business programs naturally have external interfaces, and no secondary development is required when an open interface is required; 4. When a certain business program appears When an exception occurs, it will not affect other business programs, nor will it affect the operation of the infrastructure.

The present invention adopts a reversible version control mechanism: all class libraries run by independent programs need to be released using the built-in service publisher of the infrastructure. Service publishing adopts an incremental adding strategy, and all historical versions are completely preserved, providing a basis for version rollback. Including: 1. No downtime update of production status; 2. All released versions use incremental records; 3. You can roll back to any version at any time.

The present invention adopts a unified communication protocol: two basic communication information of Http and WCF are adopted in the infrastructure, XML and JSON are used as data recording formats, and an online push function is provided at the same time. At the same time, the access of the interface program provides a standard WebService to provide support for cross-platform orientation. In the infrastructure, the client-side communication program class has been written in two languages based on JavaScript and C#, which facilitates the development of the infrastructure. Including: 1. Unified standard Http and WCF calling protocols; 2. Unified message push mechanism; 3. Unified interface calling rules; 4. Unified information compression and encryption rules; 5. Compatible with iLook and MED communication protocols.

The present invention adopts reusable Web component development: uses standard jquery class library to expand, integrates Ajax technology, realizes componentized writing of Html pages, and realizes component reuse to the greatest extent. Components are divided into: basic components, business components, combined components; basic components, realize zero coupling with business, such as lists, page turning, tree menus, etc., can be completely reused in any system developed using the infrastructure (just Use the infrastructure's front-end architecture). A business component contains a minimal atomic operation of business processing, such as a person's information display, a business add page, etc. Combination components can couple one or more basic components and business components to implement a relatively complex business operation, such as the combination of list components and page turning components to change the list information when turning pages. Including: 1. Adopt the relatively mature jQuery runtime library; 2. Use dynamic loading technology, no use or no loading; 3. Use scalable front-end architecture design to realize componentized writing of Html+Js+CSS, which is different from previous pages 4. Divide components into: basic components and business components; 5. Low coupling between components and background business.

The present invention adopts a complete log production mechanism: log records have been added to all key logical nodes of the infrastructure, and the stack trace technology is used to record the most original call location of the error method, which facilitates the rapid positioning of error information. At the same time, it provides a relatively complete log query system, which can query and count log information in multiple dimensions such as namespace, class, method, and service. In addition to the use of the infrastructure itself, the log also provides an external call interface for easy use. Including: 1. Two log recording methods: active log and passive log; 2. Use stack trace technology to record the real location of the log, independent of the output information of the program code; 3. Logs are divided into operation logs and Error log; 4. Perfect log query and statistics interface; 5. Logs can be recorded in files and databases at the same time; 6. All operating links of the infrastructure have log output.

The present invention adopts an extensible permission operation interface: on the basis of using the service mode operation and the independent program domain execution mechanism, we can check all service calls, and events are thrown at each critical stage of service calls. Provide the basis for later permission checks. Including: 1. Reserve the front-end Web component and business program call permission verification interface; 2. The permission verification can be realized by third-party programs and interfaces; 3. The mobile single sign-on interface is prefabricated.

Description of drawings

Fig. 1 is a schematic diagram of a basic development framework provided by the present invention;

Fig. 2 is a schematic diagram of connection of a basic development framework provided by the present invention.

detailed description

As shown in Figure 1, the present invention provides a basic development framework. The basic development framework of the present invention is used as a tool for reducing the amount of codes and improving the code reuse rate and code quality during the development process of programmers.

The framework of the present invention is based on Microsoft.NET Framework 4.0, written in C#, HTML, CSS, Javascript and other languages, and is suitable for developing application programs of B/S architecture and C/S architecture.

A basic development framework of the present invention includes six major parts of a UI interface display layer, a service control layer, an entity storage layer, an authority control layer, a log management layer, and a tool assembly, specifically as follows:

UI interface display layer:

The UI interface display layer is written in HTML, CSS, and Javascript languages, which is suitable for the interface development of Web application programs with B/S structure;

The UI interface display layer in the present invention adopts the concept of component design to maximize the reusability of the UI interface. Use the fully self-developed JavascriptUI framework as the basis, and provide common interface components such as: text components, drop-down selection components, group check/radio selection components, list components and menu components, etc.;

The UI interface display layer adopts an object-oriented design idea, which can run multiple instances at the same time; and components can be freely combined to form new components; components can be divided into: basic components, composite components and business components;

Basic components: the minimum functional components to realize the smallest unit function;

Composite component: composed of more than two basic components to realize the interactive function of the smallest unit;

Business component: It is composed of two or more basic components or composite components, and realizes the minimum function associated with the direct business function;

At the same time, the UI interface display layer framework can be used in combination with the popular javascript framework to achieve more functions;

The javascript framework is as follows:

jquery.IFrameWork.js

object list

object name Functional description IFrameWork_Kernel core processing object

property list

method list

Service control layer:

The service control layer is based on Microsoft.NETFramework4.0, written in C# language, combined with MVC4's RESTful standard-based WebAPI implementation; and has undergone in-depth transformation on the basis of the original MVC4, adding a unique service control mechanism: using an independent program domain run service code;

The service and the main program, and the service and the service are relatively isolated from each other, and the execution of the main program will not be affected because of a service problem. At the same time, it introduces service version management, which can upgrade and downgrade services without stopping, especially suitable for production-type application updates;

Perfect log records can record all relevant information of the request, such as call time, caller, incoming data, outgoing data and other information. Provide basic data for the analysis of service operation status in the later stage;

The specific application business process of the service control layer includes 1. Create the executor; 2. Execute the call; 3. Uninstall the executor;

Creating an executor includes (1), starting to create; (2), creating an application domain; (3), loading public assemblies; (4), judging whether the loading is successful; (5), loading private assemblies; (6) , judging whether the loading is successful; (7), if successful, the creation is completed; wherein, if the loading fails in steps (4) and (6), an exception message is thrown to the caller;

Executing the call includes (1), starting the call; (2), creating the call information object; (3), using the executor to execute the call; (4), judging whether the call is successful; (5), returning the call execution result; (6) , the call is completed; wherein, if the call fails in step (4), an exception message is thrown to the caller;

The uninstall executor includes (1), start to uninstall; (2), obtain the application domain; (3) determine whether the program can be uninstalled; (5), uninstall the application domain; (6) uninstall complete; wherein, step (3) If the unloading fails, an exception message will be thrown to the caller.

Physical storage layer:

The entity storage layer is based on Microsoft.NETFramework4.0, written in C# language, combined with EntitiesFramework entity framework technology. Appropriate modifications have been made on the technical basis of the original frame. Added construction methods and control interfaces suitable for enterprise application development;

The entity storage layer includes database connection pool, SQLHelp helper class, outer wrapper class and SQLXML reading and management helper class;

Database connection pool:

Provide related public methods and their functional descriptions about the data connection pool;

Mainly used for data persistence operations;

Including operations related to data persistence such as creating data connections, releasing data connections, statement execution, and things;

Four SQLHelp help classes:

The simplest call that can be used, that is, you only need to provide SQL, and you don’t need to care about other matters such as data connection, and you can get the execution result;

It can support SQL variable replacement and insertion to prevent splicing SQL-style SQL injection;

Can support SQL transactions, users only need to declare whether to use transactions, no need to participate in the specific implementation;

Can support multiple database types, such as: MsSQL, MySQL, ORACLE, etc., with MSSQL as the main support object, and can support MsSQL2005 or later;

It can support the independent storage function of SQL text; that is, the SQL text does not appear in the program code, and the SQL text can be modified in the case of zero modification of the program code by using the method of in vitro recording and reference, but at the same time, it should meet certain security processing methods , to prevent the SQL text from being illegally modified;

ORM object storage capable of supporting the Microsoft Entity Model;

Outer wrapper class:

The simplest call that can be used, that is, you only need to provide SQL, and you don’t need to care about other matters such as data connection, and you can get the execution result;

It can support SQL variable replacement and insertion to prevent splicing SQL-style SQL injection;

Can support SQL transactions, users only need to declare whether to use transactions, no need to participate in the specific implementation;

It can support multiple database types, such as: MsSQL, MySQL, ORACLE, etc., with MSSQL as the main support object, and can support MsSQL2005 or later versions.

The main business process includes: 1. Initialize the connection pool; 2. Start the connection pool service; 3. Apply for a connection in the connection pool; 4. Release the applied database connection object; 5. Stop the connection pool service; 6. Check the connection pool whether the connection is valid;

1. Initializing the connection pool includes: setting the connection pool as a new object state; initializing the connection string, connection pool type, database type, maximum and minimum number of connections, number of connections created each time, actual number of idle connections reserved, whether to create The thread continues to work with the variable createThreadProcessRun, the actual connection list, the number of connections to be created createThreadProcessTemp_inside; create a thread and create a monitor at the same time, register the connection check event; end.

2. Start the connection pool service: set the initialization working mode to 0, the thread blocking state createThreadProcessRun=true; the minimum number of connections; judge whether the connection pool state has been created; start the thread according to the state; initialize the thread to prepare the thread for the connection pool, and start the monitor .

3. Apply for a connection in the connection pool: determine the application connection level; allocate ReadOnly level connection, High level connection, None level connection and Bottom level connection; add this connection to the connection list in use; update attributes; return DbConnection connection object; end.

4. Release the database connection object of the application: find the connection to be released from the connection list in use; determine whether the connection is invalid; otherwise, update the connection properties so that it can be allocated; remove the connection from the connection list in use; Update connection pool properties; end.

5. Stop the connection pool service: clear the connection list in use; stop the monitor timing; release all actual connections; set the connection pool to stop state; update the connection pool properties; end.

6. Check whether the connection in the connection pool is valid: turn off the monitor timing to ensure that only one event processing process is running at the same time; loop the actual connection list; test whether the connection expires; if yes, close the connection and remove it from the actual connection list; update Connection pool attributes; whether the idle actual connection is smaller than the reserved actual idle connection; start creating thread working mode; enable monitor timing; end.

SQLXML reading and management helper class:

The independent storage function of SQL text; that is, the SQL text does not appear in the program code, and the SQL text can be modified in the case of zero modification of the program code by using the method of in vitro recording and reference in the program, but at the same time, it should meet certain security processing methods to prevent The SQL text was illegally modified.

SQLXML reading and management help business processes include 1. Instantiation; 2. File monitoring Change; 3. File monitoring Deleted; 4. File monitoring Renamed; 5. Obtaining SQL statements according to the serial number of SQL statements; SQL entity;

1. Instantiation: determine whether there is a SQLXML path; otherwise, create a path; determine whether a monitor exists; otherwise, create a monitor; start the monitor; register monitoring events; end.

2. File monitoring Change: Get the SQLXML file name; remove the file from the cache; get the SQL entity according to the SQLXML file path; if there is no local SQLXML file, or the serial number and the file name are inconsistent, rename it to the source file name +.bak extension; determine that there is a changed SLQXML in the cache; remove the old cache and add a new cache; end.

3. File monitoring Deleted: get the SQLXML file name; remove the file from the cache; get the SQL entity from the cache; remove the old cache; end.

4. File monitoring Renamed: Get the SQLXML file name; remove the file from the cache; get the SQL entity according to the SQLXML file path; if there is no local SQLXML file, or the sequence number and file name are inconsistent, rename to the source file name +.bak Extension; select the changed SLQXML in the cache; remove the old cache and add a new cache; end.

5. Obtain the SQL statement according to the serial number of the SQL statement: determine whether there is a SQLXML path; otherwise, create a path; determine whether a monitor exists; otherwise, create a monitor; start the monitor; register a monitoring event; end.

6. Obtain SQL entities according to the path of the SQLXML file: obtain the name of the SQLXML file; remove the file from the cache; obtain the SQL entity according to the path of the SQLXML file; if there is no local SQLXML file, or the sequence number and file name are inconsistent, rename it to the source file name+bak extension; determine that there is a changed SLQXML in the cache; remove the old cache and add a new cache; end.

Authority control layer:

The authority control layer is based on Microsoft.NETFramework4.0 and written in C# language; it is divided into several control dimensions: function point management, role management, role authority management and role personnel management.

The authority control layer is used to control the automatic loading and registration of the service layer, eliminating the problem of manual preparation of function points that are prone to errors;

The interface design is adopted for personnel, which can easily access third-party personnel information and SSO control information to achieve seamless expansion.

Log management layer:

The log management layer is based on Microsoft.NETFramework4.0 and written in C# language; it includes three aspects: system log, business log, and user log;

System log: integrated in the service control layer, entity storage layer and authority control layer, automatically records all call log information;

Business log: integrated in the service control, self-recording all business data log information;

User logs: Released in the form of an open interface, and the developers call and record relevant log information in the program code according to their own needs;

All log information supports log file output and log data output functions, and provides supporting log viewing and management tools.

Tool assembly:

The tool assembly is based on Microsoft.NETFramework4.0 and written in C# language; it integrates the collection of non-business methods commonly used in enterprise software development, and is divided into: character processing program collection, image processing program collection, serialization program processing collection, plus Decryption program processing collection, compression and decompression program processing collection, etc.

The sub-modules in the basic framework of the present invention can form a relatively independent operating mechanism, and the modules adopt a low-coupling design, so it can satisfy direct reference and use of a certain module, and provide support for satisfying various development modes.

The development mode supported by the infrastructure of the present invention includes primary development, intermediate development and advanced development;

Primary development: basic three-tier architecture development model

The infrastructure can meet the basic three-tier architecture development, namely, presentation layer (UI interface display layer), business layer (service control layer), data layer (entity storage layer), and standard MVC architecture development. Using this development mode only needs to directly apply the public assembly of the infrastructure, the data connection pool, and the mobile service SDK interface for simple development. This development mode can be used to develop standard .netB/S architecture codes, that is, the development of common Aspx pages;

On this basis, you can also use the front-end JavaScript class library of the infrastructure to develop Html components, and the communication layer class library in the infrastructure to develop relatively complex business systems.

Intermediate development: simple business service development model

Use the standard development specification of the basic framework to develop the service method; all business methods are called and executed using the standard communication protocol. The front end can use both Aspx pages and Html pages, or the WinFrom program of the C/S architecture to call. The basic structure has been Provides B/S and C/S two client calling assemblies;

This development mode is more suitable for projects that require a large number of open interfaces. All business methods run in the form of services, which meet the two calling methods of WebService and Http, and use standard XML and Json as the carrier of information records to meet cross-platform calls;

At the same time, this development model is compatible with the service of the standard C# class library. Through the service publisher, the service operation can be performed without modifying the source code. It is compatible with the business processing class library and the first three-tier architecture development model in the primary development. Three-party standard C# class library.

Advanced development: centralized management control development mode

The development method of this development mode is exactly the same as the above two development modes, which is mainly reflected in the difference in installation and deployment; it can be deployed in a single business system or in multiple business systems, and all businesses are run as services, compatible with previous Business classes produced by two development modes;

The main advantage of this model lies in centralized management and control. Detailed logs are generated for all services’ release, operation, update, deactivation, and other operations, and at the same time, authority control can be extended. The usage of the system is clear at a glance.

The present invention is not limited to the above-mentioned best implementation mode, anyone can draw other various forms of products under the inspiration of the present invention, but no matter make any changes in its shape or structure, all those with the same or similar features as the present application Approximate technical solutions all fall within the protection scope of the present invention.

Claims (10)

1. a foundational development framework, it is characterized in that: described foundational development framework uses C#, HTML, CSS and Javascript language development, comprising: UI showing interface layer, service control layer, entity accumulation layer, control of authority layer, log management layer and implementing procedure collection;

Described UI showing interface layer, control of authority layer, service control layer are connected successively with entity accumulation layer;

Described UI showing interface layer realizes cross-platform application and development by the assembly that HTML, CSS and JavaScript are formed, is applicable to the interface development of the web application of B/S structure;

Described service control layer, entity accumulation layer, control of authority layer, log management layer and implementing procedure collection all adopt based on Microsoft.NETFramework4.0, use C# language to write.

2. a kind of foundational development framework according to claim 1, it is characterized in that: described UI interface adopts based on the JavascriptUI framework of independent development, UI interface assembly comprises text component, drop-down selection assembly, grouping final election/single choice assembly, list element and menu component; UI interface assembly can carry out independent assortment, forms new assembly, and it comprises infrastructure component, composite component and Service Component;

Described infrastructure component is minimized functional module, for realizing minimum unit;

Described composite component is combined by plural infrastructure component, for realizing the interaction of minimum unit;

Described Service Component is combined by plural infrastructure component or composite component, for realizing and the minimizing of direct writing function association.

3. a kind of foundational development framework according to claim 1, it is characterized in that: described service control layer makes service and master routine, relatively between service and service isolates operation, introduce service release management simultaneously, can to upgrade to service in non-stop-machine situation, process of demoting; Described service control layer embody rule method comprises establishment actuator, performs and call and unload actuator.

4. a kind of foundational development framework according to claim 3, is characterized in that: described establishment actuator comprises (1), starts to create; (2), Application Domain is created; (3), common program collection is loaded; (4), judge whether to load successfully; (5), private assembly is loaded; (6), judge whether to load successfully; (7), success has then created; Wherein, load unsuccessfully then to called side throw exception information in step (4) and step (6).

5. a kind of foundational development framework according to claim 3, is characterized in that: described execution is called and comprised (1), starts to call; (2), recalls information object is created; (3), use actuator to perform to call; (4), judge whether to call successfully; (5), return and call execution result; (6), called; Wherein, the middle malloc failure malloc of step (4) is then to called side throw exception information.

6. a kind of foundational development framework according to claim 3, is characterized in that: described unloading actuator comprises (1), starts unloading; (2), Application Domain is obtained; (3) whether determining program can unload; (5), Application Domain is unloaded; (6) unloaded; Wherein, the middle dismount failure of step (3) is then to called side throw exception information.

7. a kind of foundational development framework according to claim 1, is characterized in that: described entity accumulation layer comprises database connection pool, SQLHelp helps class, outer envelope class and SQLXML to read and management helps class;

Described database connection pool is used for data persistence operation, it comprise create data link, release data cube computation, statement perform and the operation of relevant data persistence;

Described SQLHelp helps class to support, and SQL variable is replaced insertion, the separate, stored of SQL affairs, various database types, SQL text and the ORM object of Microsoft's solid model and is stored;

Described outer envelope class supports that SQL variable replaces insertion, SQL affairs and various database types.

8. a kind of foundational development framework according to claim 1, is characterized in that: described control of authority layer comprises function point administration module, Role Management module, role-security administration module and role's personal management module; Control of authority layer adopts interfaceization design, for accessing third-party personal information and SSO control information.

9. a kind of foundational development framework according to claim 1, is characterized in that: described log management layer comprises system journal, business diary and user journal;

System journal is used for being integrated in that Service controll becomes, entity accumulation layer and control of authority layer, automatically records allly to call log information;

Business diary is used for being integrated in Service controll, makes by oneself and records all business datum log informations;

User journal externally discharges for adopting the form of open interface, calls the relevant log information of record by developer according to self needing in program code.

10. a kind of foundational development framework according to claim 1, is characterized in that: described implementing procedure collection comprises the set of character handling procedure, picture processing program set, serialization process process set, the set of encryption and decryption routine processes and compressordecompressor process set.