Browser quick access method and system

Abstract

The present invention provides a browser quick access method, which includes: setting a base unit in a local browser. The local browser receives the user access request. The local browser judges whether there is current access routing information in the pre-stored routing information of the base unit, and according to the judgment result, chooses to call the pre-stored routing resource matching from the current access routing information or send a resource call request to the remote server according to the current access routing information. Reduce the volume of resources obtained by the browser and the number of requests, separate public dependencies and business services, reduce server traffic, reduce business server pressure, and speed up website opening. Greatly reduce the size of the service and speed up the speed of building and packaging, shortening the development time. When you need to add global functions, you only need to add them in the base service, saving development and testing time. At the same time, the invention also provides a quick access system of the browser.

Description

technical field [0001] The invention relates to the Internet field and is applied to fast browsing of browsers. The invention specifically relates to a browser fast access method and system. Background technique [0002] The update and iteration of the existing front-end architecture is very fast, and there should be similar ideas in the market, that is, service aggregation. However, based on the front-end pedestal service, it has not been found yet. [0003] In the existing technology, large-scale front-end services generally adopt the method of multiple services in a single domain name, and request different front-end services through different request routes. The current technologies are all superficial service aggregation, but in fact there is no To achieve real service aggregation, it is only through the forwarding layer through different routes of a single domain name that requests to different servers are realized. [0004] This architecture is very simple, and arc...

AI Technical Summary

Problems solved by technology

[0006] 1. The service does not achieve real aggregation, but only the aggregation of performance;

[0007] 2. Each single service has a large number of the same dependencies, and the dependencies are redundant, resulting in large service volume and slow construction speed

[0008] 3. Each single service is coupled with public dependent resources. When public dependent resources are modified, each single service needs to be modified, which wastes developer time and is easy to miss

[0009] 4. Every single service needs to be re-tested after updating, which wastes the time of testers and is easy to miss

[0010] 5. Each service contains a large number of non-business codes, and coupled with business codes, users need to pull these codes every time, resulting in a large number of network requests, slowing down the speed of resource pulling, and reducing user experience

[0011] 6. When global functions need to be added, corresponding code needs to be added to each service, and the process of packaging, testing and launching is performed, which is not only redundant code, but also a waste of time

[0012] 7. The public dependency package is coupled with business code, so that the public dependency package cannot use network distribution technology and browser caching technology

[0013] The above defects are due to the fact that the design of the architecture is updated with the iteration of technology. Before the computer web has not developed into a giant stone application, the basic architecture of single domain name single service and single domain name multi-service is not a big problem. With the development of technology and the increase of demand, front-end applications are becoming more and more complex, and there are more and more services under a single domain name, and the coupling degree between services is also increasing. At the same time, there are more and more dependencies on services. More and more global functions are added, which gradually makes it difficult for developers to develop and maintain, and difficult for testers to test, and users need to pull a large number of long-term dependent codes every time

Images