Browser front-end architecture system capable of being developed separately from rear-end architecture

Abstract

The invention provides a browser front-end architecture system capable of being developed separately from a rear-end architecture. The browser front-end architecture system comprises an access layer,an HTML single-page application module, a view module, a webpack module packer, a control module and a model layer. The method and the device are used for solving the problems that each page of an existing browser is time-consuming in requesting static resources, variable conflicts occur when js files are introduced, DOM element rendering is slow and performance is poor when the page is locally refreshed, and have the characteristic of improving the performance of a front-end architecture system.

Description

technical field [0001] The invention relates to the technical field of browser construction, in particular to a browser front-end architecture system that can be developed separately from the back-end architecture. Background technique [0002] As Internet applications become larger, business logic processing becomes more and more complex, and users have higher and higher expectations for a good experience, in this case, if we continue to maintain the page-based development method, it will inevitably cause many problems. Problems, such as time-consuming requests for static resources for each page, variable conflicts when importing js files, slow rendering of DOM elements when the page is partially refreshed, poor performance, etc., and because of the rapid development of front-end technology, different browsers are compatible with ES Not one, which leads to the inability of traditional development methods to use many new syntaxes since the ES6 version. Contents of the inve...

AI Technical Summary

Problems solved by technology

[0003] The present invention provides a browser front-end architecture system that can be developed separately from the back-end architecture, which is used to solve the time-consuming request of static resources for each page of the existing browser, variable conflicts when introducing js files, and DOM element rendering when the page is partially refreshed. To solve the problem of slowness and poor performance, the technical solutions adopted are as follows:

Images