WO2015176519A1 - Distributed collaborative method for improving application efficiency of web browser - Google Patents

Abstract

Disclosed is a distributed collaborative method for improving application efficiency of a Web browser. The method enables functions superior to those of common browser sides by means of a local Web server side module running in an intelligent terminal. The local Web server side module interacts with a remote Web service module comprising a cloud server to form one node of distributed collaborative computing. The browser obtains webpage files by interacting with the local Web server side module and displays the webpage files. The interaction between the browser and the local Web server side module is free of influences of network conditions, and the response speed and fluency of the browser can be significantly improved. The present invention eliminates the defect that an App client of a conventional intelligent terminal needs to be updated frequently, has compatibility and cross-platform commonality of a Web application system with B/S architecture, overcomes the defects in functions and real-time interaction of a Web application browser side of a conventional browser, enhances user experience, and can make up for the defect that the intelligent terminal has insufficient computing capacity.

Description

 A distributed collaborative method for improving the efficiency of web browser applications

Technical field

 The present invention relates to network data transmission technologies, and more particularly to a distributed collaboration method for improving the efficiency of a web browser application.

Background technique

 At present, in the distributed collaborative computing of intelligent terminals and remote Web service programs at home and abroad, the main method adopted is the C/S architecture (ie App mode), B/S architecture (ie browser mode), SOA architecture (ie web service mode). However, there are certain deficiencies.

 (1) C/S architecture (ie App The advantage of the method is that the interaction ability is excellent. The disadvantage is that it is very troublesome for the user to update the program version frequently. For the developer, it is necessary to adapt the intelligent terminal with different hardware versions and different system versions, resulting in inefficiency.

 (2) The advantage of the B/S architecture (ie browser mode) is that the update is done on the remote web server, and the user does not need to download the app. Client, but this method is less interactive, has delayed response, is not powerful enough, lacks master control, and is prone to information loss and other errors.

 (3) SOA architecture (ie Web Service) Mode) too large and bloated, not suitable for direct deployment to common smart terminals, especially mobile smart terminals, mobile terminal hardware performance is limited, Web Service It's easy to run slowly, and it also causes the browser to respond slowly.

 (4) The problem of decentralized control is caused by many operations directly through the browser, and each Web Server is required. Cooperate with each other, there is no master point (the browser is not the master). This design is difficult and error-prone to implement. For example, in some trading scenarios, there may be a situation in which a failure causes a transaction to be interrupted and money is lost.

 (5 Although the hardware of today's mobile devices is developing rapidly and software optimization is strengthened, a large number of practical software for mobile intelligent terminals have been born, but the user's demand for hardware capabilities is not limited. The hardware of the mobile platform must consider volume, power consumption, heat dissipation, etc. And other issues, can not improve the hardware performance without limit, especially due to the limitation of atomic diameter, now CPU performance has rapidly developed to a bottleneck, and more needs to be processed through distributed collaborative computing.

Summary of the invention

 The object of the present invention is to overcome the above-mentioned deficiencies of the prior art and to provide an improvement of the Web. A distributed collaborative method for browser application efficiency, the specific technical solution is as follows.

 A distributed collaborative method for improving the efficiency of a web browser application, the method comprising:

 Through a local web server module running behind the smart terminal browser on the smart terminal and one or more remote webs Service module, which realizes the distributed collaborative computing Web service, and communicates directly with the local Web server module through the browser to improve the browser response speed; As a general middleware, the service enables intelligent terminals to communicate with the remote web based on HTTP protocol and XML documents. The service module jointly implements the foregoing distributed collaborative computing; the smart terminal browser does not directly exchange data with the remote web service module including the cloud server, but with the web running in the local background. The server module exchanges data, and the local web server module exchanges data with various remote web service modules; the browser sends a request to the local web server module, the local web The server module parses the request and gives the browser the required files; the browser quickly refreshes some pages through AJAX and other dynamic dynamic web technologies, and the local web server module uses the HTTP protocol. XML document-based communication methods exchange data with remote web service modules including cloud servers, and convert user requests into distributed computing tasks to the remote web. The service module obtains the layout file and continuously refreshes the local layout file to obtain the layout change in time.

 Further, the local web service as a general middleware is specifically:

 Run a small local web server module in the background of the smart terminal as a common middleware; the local web service The end module does not contain a user interface and does not involve control of the underlying hardware; the local web server module can serve as a client to send requests to a remote web service module including a cloud server, or as a local The web server module receives the request from the smart terminal browser; the calculations and functions that the browser cannot complete are sent to the local web server module through the request to make full use of the smart terminal hardware for calculation or remote Web service module communication, which implements distributed computing of nodes on the network; HTTP between the local web server module and the local browser The protocol exchanges data, which can be returned to the browser to render the files required by the user interface; the XML between the web server module and the remote web service module is customized based on the HTTP protocol. The format of the protocol for data transmission; in addition, the remote Web service module is also based on the same protocol for data transmission.

 Further, in the distributed collaborative computing: the local browser cannot directly communicate with the remote web service module, but only by accessing the local Web server module to obtain files; each role communicates via HTTP protocol, HTML communication between local browser and local web server module, and local web Between the server module and the remote web service module and between the remote web service module and the remote web service module is a custom unified XML based on the HTTP protocol. The format of the protocol is communicated.

 Further, the XML exchange data between the local web server module and the remote web service module Formatted protocols include:

 The format tag contains the following information: role information, code to initiate the request, destination to address, extension information, XML The timestamp when the file is sent, if necessary, can add the required label under the extended information label during communication, otherwise the content of the extended information label is empty.

 Compared with the prior art, the present invention has the following advantages and technical effects:

 The invention passes through a local web server module running on the smart terminal and running behind the browser of the smart terminal and the remote web service Modules work together to implement distributed Web services, enabling browser responsiveness and compatibility issues. The local web server module compared to a thin client such as a browser More calculations can be performed according to actual needs, and distributed collaborative computing can be implemented together with the remote Web service module to make full use of the performance of the intelligent terminal and enhance the user experience. The local web server module Relying on the browser to render the user interface but not relying on a specific browser. The local web server module can exist as both a client and a server, and can act as a client to a remote web service module. Initiate a request, request distributed execution of the application, and obtain the corresponding interface layout file. The local web server module can respond to requests from a local browser, and the browser can pass the local web server module Send requests to get HTML files and other files related to interface rendering, and if necessary, automatically refresh some pages via dynamic web technologies such as AJAX. The local web server module Can be used as a client to connect to a remote web service module Update the interface layout file in the background. Since the transmitted data only has the interface layout file and can be transmitted in the background, the browser is not required to be called, and the browser is only used to present the interface, so the response speed is greatly improved, and even due to network congestion and other problems. The local Web server module Occasionally, the page layout file cannot be obtained, and the page cannot be displayed, because it can be returned to the HTML file that the browser has stored locally; the software receives the XML. After the file is parsed out the interface layout file and can automatically call the browser to display the file.

 Each remote web service module has the same status and can act as a client to initiate a request and as a server to receive requests. Various web The server modules communicate in a unified format with XML files.

 The user sends a request to the local web server module by operating on the browser, the local web server module The request is then parsed and then a corresponding formatted XML format request is generated, and then a request is made to the remote web service module, which receives the remote web service module The returned interface layout file can automatically call the browser to display the file.

 Local and remote Web by adding a local web server module running in the background Distributed collaborative computing of service modules, local does not need to be like C/S The application updates the application as often as the architecture. Displaying the user interface through the browser also solves the compatibility problem. Since the partial page can be refreshed by continuously obtaining the local page file, and the intelligent terminal can obtain the update of the page layout from the remote web service module in time, and does not need to transmit most of the pictures required by the transmission interface, the network can be added without The response speed is significantly improved in the case of traffic consumption. Relative to B/S The architecture can significantly improve the ability to interact. And the local web server module can more easily expand functions, such as encrypting and sending passwords, uploading and downloading breakpoints, and the like. This allows you to extend the functionality of your browser without developing plug-ins for specific browsers. In addition, the invention is partially logically similar The SOA architecture, but more lightweight than the SOA architecture, retains only the required parts, enabling it to be deployed to general smart terminals, including mobile smart terminals.

DRAWINGS

Figure 1 is a schematic diagram of the exchange of data in the present invention;

2 is a schematic flow chart of the operation of the smart terminal in the present invention.

FIG. 3 is a schematic diagram of a running process after receiving a request from a local browser according to the present invention.

detailed description

In order to solve the shortcomings of the traditional smart terminal App client, it is necessary to maintain the compatibility of the B/S architecture Web application system and cross-platform universality, solve the shortcomings of the web application browser function and real-time interaction, enhance the user experience and make up for The shortcomings of the lack of computing power of the intelligent terminal, the following provides a distributed collaborative method for improving the efficiency of the application of the web browser, through a local operation running on the smart terminal The web server module is more powerful than the general browser.

As shown in FIG. 1 , the web server module runs in the background of the user's smart terminal and interacts with the user via a browser. This process is performed according to the Http protocol, and the local web server module becomes a collaborative computing. The node exchanges data with the remote web server module. This process is based on the Http protocol and is carried out through a specific protocol. The protocol has an XML file format, and the data exchange between the remote web service modules is also performed. Follow the same agreement.

For the current cloud application developers need to refer to the transmission specification to develop the data link layer, the transmission protocol of the present invention is built on the standard HTTP protocol, and the request for directly obtaining the file is GET, and is used for the browser to access the local service to obtain the file. .

The local web server module exchanges data with the remote web service module and exchanges data between the remote web service module and the remote web service module. The POST request is implemented by sending an XML file.

Internal tags include, but are not limited to, ROLE (content is network role information), DIRECT (content is target action), NAME (content is name), HREF (content is network path), MODIFYTIME (content is the last modification time of the request file), EXTRAINFORMATION (content is additional information).

The overall process of running the local web server module disclosed in the present invention is as shown in FIG. 2 .

Step 201: The local web server module waits for a request from the local browser.

Step 202: The local web server module receives the request of the local browser. The first request is generally a GET request, and the browser checks the list of the requests that can be obtained through the request.

Step 203: The local web server module returns a list webpage file to the browser.

Step 204: The web server module receives and parses the request sent by the browser, and starts to provide a specific service to the user according to the user's needs;

Step 205: Waiting for the user to terminate the service being provided;

Step 206: continuously generate a request in an XML format that meets the requirements as long as the user does not terminate the service;

Step 207: request the package by using Http POST and send the request to the remote web service module;

Step 208: Acquire an interface layout file and update the local interface layout file. If the steps 207 and 208 fail, the local layout file remains as it is, waiting for the next update, and the browser still obtains the old file without appearing. Unable to get the file;

If the user stops acquiring the service, then go to step 209.

Step 209: Generate a request to terminate the service application according to the specified format.

Step 210: By requesting the package with Http POST and sending the request to the remote web service module.

The local web server module sends an XML file carrying the request information through the POST request, and the remote web service module processes the request and returns the corresponding interface layout file, and the local web server module can receive the file and invoke the browser display, because the present The Web service module in the invention is not a ready-made Web service program, but is based on the underlying Socket programming, so it has the ability to initiate requests.

FIG. 3 illustrates the processing manner of the web server module disclosed by the present invention after receiving a local browser request:

Step 301: Acquire specific content requested by the browser;

Step 302: Determine the browser requirement, the local web server module and the remote service module agree on the standard way of writing the webpage file, submit the GET request, or send the request for obtaining the file through the POST request as a method for obtaining the file, if the request of the browser is to obtain the file Go to step 303, if it is an interaction request with the remote web service module (including obtaining service, terminating service, submitting data, etc.), then skip to step 304;

Step 303: Determine whether the file exists, and return the corresponding file according to the logic shown in the figure;

Step 304: Parsing the request sent by the browser and packaging the request into an XML format according to a prescribed format;

Step 305: Returning to the browser a temporary loading page, the page is automatically refreshed, and the local web server module updates the file after obtaining the interface layout file from the remote web service module;

Step 306: Send the request of step 304 to the remote web service module.

The local web server module exists in the background to start a service only for the local browser, and the local browser obtains the file by accessing the local web server module. After the browser sends the request to obtain the application for the first time, the local web server module will return the loading page, and then the file will be updated in the background. The browser quickly refreshes the page through dynamic webpage technology such as AJAX to update the page at the first time.

For example, in the process of network transmission, there may be more than 5 routers, the delay may reach 100ms, and there may be a bandwidth bottleneck of 100K in the middle. So directly use the browser to access the remote Web service module, the display will be prone to dullness. The user experience is affected. After the local web server module communicates with the remote web service module and obtains the file, the browser can communicate with the local web server module to obtain the corresponding file, and the local virtual bandwidth is above 1G. The delay is less than 1ms, so that using the browser to display the page will not be responsive. In addition, the local web service module can perform technical processing on the data, similar to the cache of the streaming media player, so that the browser display is smoother.

Claims (4)

1. A distributed collaborative method for improving the efficiency of a web browser application, the method comprising:

   Realizing distributed collaborative computing Web services through a local web server module running behind the smart terminal browser and one or more remote web service modules running on the smart terminal, and directly communicating with the local web service through the browser The end module communication realizes the improvement of browser response speed; the local web service is used as a general middleware, so that the intelligent terminal can realize the custom application layer communication method based on HTTP protocol and XML document together with the remote web service module. The foregoing distributed collaborative computing; the smart terminal browser does not directly exchange data with the remote web service module including the cloud server, but exchanges data with the web server module running in the local background, and the local web server module Data exchange with various remote web service modules; the browser sends a request to the local web server module, the local web server module parses the request, and gives the browser the required files; the browser passes AJAX and other dynamic dynamics Web technology quickly refreshes some pages, the local web server module passes HTTP protocol, XML The file-based communication method exchanges data with the remote web service module including the cloud server, and converts the user request into a distributed computing task information to the remote web service module, obtains the layout file, and continuously refreshes the local layout file. Get timely changes in layout.
2. The distributed collaborative method for improving the efficiency of a web browser application according to claim 1, wherein the local web service as a general middleware is specifically:

   Running a small local web server module in the background of the smart terminal as a general middleware; the local web server module does not include a user interface, and does not involve control of the underlying hardware; the local web server module can As the client sends a request to the remote web service module including the cloud server, the local web server module can also receive the request from the smart terminal browser; the calculation and function that the browser cannot complete is sent to the local web through the request. The server module can fully utilize the intelligent terminal hardware for computing or communicate with the remote web service module to implement distributed computing of nodes on the network; the local web server module and the local browser exchange data based on the HTTP protocol, Returning to the browser to present the files required by the user interface; the web server module and the remote web service module perform data transmission in a customized XML format protocol based on the HTTP protocol; in addition, the remote web service modules are also Data transmission based on the same protocol.
3. The distributed collaborative method for improving the efficiency of a web browser application according to claim 1, wherein in the distributed collaborative computing, the local browser cannot directly communicate with the remote web service module, and only Access the local web server module to obtain files; each role communicates via HTTP protocol, and the local browser and the local web server module communicate with each other, and between the local web server module and the remote web service module. And the remote web service module and the remote web service module communicate with a customized unified XML format protocol based on the HTTP protocol.
4. The distributed collaborative method for improving the efficiency of a web browser application according to claim 1, wherein the XML format protocol for data exchange between the local web server module and the remote web service module comprises:

   The format tag contains the following information: role information, the code of the originating request, the target address, the extended information, and the timestamp when the XML file is sent. If necessary, the required tag can be added under the extended information tag when communicating, otherwise the extended information tag The content is empty.