WO2016066048A1 - Method, apparatus and system for updating web application - Google Patents

Abstract

A method, apparatus and system for updating a Web application. The method comprises: receiving a resource update file for an independent presentation layer in a Web application (301), wherein the presentation layer has a resource file, the resource file has load time, and the resource update file has modification time; judging whether the modification time is greater than or equal to previous load time (302); and if yes, loading the resource update file in the presentation layer (303). By means of the method, the presentation layer is managed independently, so that when the presentation layer is updated, modifications can be made and resource update files can be released directly at the presentation layer, back-end code update does not need to be considered, and traditional complicated release processes such as code merging, compiling, and packing are not required; therefore, release processes are greatly reduced, release is accelerated, and at the same time, a risk of update is lowered, stability of the presentation layer is improved, and update efficiency is greatly increased.

Description

Method, device and system for updating web application Technical field

The present application relates to the field of network technologies, and in particular, to a method for updating a web application, an update device for a web application, and an update system for a web application.

Background technique

With the development of Internet technology, Web (web) applications are more and more widely used as the basis for the implementation of dynamic websites. Web applications can be Java (an object-oriented programming language), PHP (Hypertext Preprocessor, hypertext pre-preparation). Processing languages), Python (an object-oriented, literal translation computer programming language) and many other language implementations, providing web services such as web browsing for browser-based client users.

For Web applications, in order to facilitate development and maintenance requirements, it is necessary to divide the level of Web application logic so that different developers can simultaneously develop layers.

Among them, the layering generally includes a view layer, which can be an interface that the user sees and interacts with. The Internet industry often adjusts the displayed content, changes user interaction, copywriting, etc. to enhance the user experience or release new functions.

In the traditional publishing process, all code (including view layer) modifications use a unified publishing process: modify code → code merge → compile → package → code distribution → deployment.

It can be seen that in the whole process, modifying the view layer requires a complicated release process, and the update time is very long. Moreover, each update requires a full release of the web application, and the publishing process occupies a large amount of network resources.

During the release process, the application container cannot be serviced because it needs to be restarted. Therefore, the cluster release process requires very complicated operations such as stopping traffic, redeploying, and enabling traffic.

The business logic risk of modifying the code in the above release process is very high. Each time the redeployment loads all resource files, including view files and back-end logical files, the risk of each release is uncontrollable and the stability is potentially risky.

Therefore, a technical problem that needs to be solved urgently by those skilled in the art is how to propose a method for updating a web application, which is used to reduce the release process and reduce the consumption of network resources. Reduce risk and increase stability.

Summary of the invention

The technical problem to be solved by the embodiments of the present application is to provide a method for updating a web application, which is used to reduce the release process, reduce the consumption of network resources, reduce risks, and improve stability.

Correspondingly, the embodiment of the present application further provides an update device for a web application, which is used to ensure implementation and application of the foregoing method.

In order to solve the above problem, the present application discloses a method for updating a web application, including:

Receiving a resource update file for a separate presentation layer in the web application; the presentation layer has a resource file, the resource file has a load time, and the resource update file has a modification time;

Determining whether the modification time is greater than or equal to the last load time; if yes, loading the resource update file in the display layer.

Preferably, the presentation layer is used to load an interaction interface in a web application;

The display layer includes at least one of the following resource files:

Web documents, template files, images, cascading style sheets, script objects.

Preferably, the resource update file is an incremental file that is updated for resource files in the presentation layer.

Preferably, the step of receiving a resource update file for a separate presentation layer in the web application comprises:

The resource update file for the independent presentation layer in the web application is stored in the corresponding directory;

The modification time is configured for the resource update file.

Preferably, the step of loading the resource update file in the display layer comprises:

Starting a template engine corresponding to the display layer;

The template update engine loads the resource update file in the directory.

Preferably, the web application further includes an application layer, the presentation layer and the application layer are independent of each other, and the presentation layer runs in the same web container as the application layer.

The embodiment of the present application further discloses an update device for a web application, including:

a resource update file receiving module, configured to receive a resource update file for an independent presentation layer in the web application; the display layer has a resource file, the resource file has a loading time, and the resource update file has a modification time;

a time judging module, configured to determine whether the modification time is greater than or equal to a previous loading time; if yes, calling a resource update file loading module;

a resource update file loading module, configured to load the resource update file in the presentation layer.

Preferably, the presentation layer is used to load an interaction interface in a web application;

The display layer includes at least one of the following resource files:

Web documents, template files, images, cascading style sheets, script objects.

Preferably, the resource update file receiving module includes:

a storage submodule, configured to store a resource update file for a separate presentation layer in the web application into a corresponding directory;

The configuration submodule is configured to configure a modification time for the resource update file.

Preferably, the resource update file loading module includes:

a sub-module, configured to start a template engine corresponding to the display layer;

Loading a sub-module for loading a resource update file in the directory by using the template engine.

The embodiment of the present application further discloses an update system for a web application, where the system includes a publishing platform and one or more servers;

The publishing platform includes:

a resource update file publishing module, configured to issue a resource update file for an independent presentation layer in the web application;

The server includes:

a resource update file receiving module, configured to receive a resource update file for an independent presentation layer in the web application; the display layer has a resource file, the resource file has a loading time, and the resource update file has a modification time;

a time judging module, configured to determine whether the modification time is greater than or equal to a previous loading time; if yes, calling a resource update file loading module;

a resource update file loading module, configured to load the resource update file in the presentation layer.

Preferably, the presentation layer is used to load an interaction interface in a web application;

The display layer includes at least one of the following resource files:

Web documents, template files, images, cascading style sheets, script objects.

Preferably, the resource update file receiving module includes:

a storage submodule, configured to store a resource update file for a separate presentation layer in the web application into a corresponding directory;

The configuration submodule is configured to configure a modification time for the resource update file.

Preferably, the resource update file loading module includes:

a sub-module, configured to start a template engine corresponding to the display layer;

Loading a sub-module for loading a resource update file in the directory by using the template engine.

Compared with the background art, the embodiments of the present application include the following advantages:

In the embodiment of the present application, the display layer is independently managed, and when the display layer is updated, the display layer can be directly modified, and the resource update file is released, and the update of the back-end code can be avoided, and the code is not merged, compiled, and packaged. Such complex traditional publishing process greatly reduces the release process and speeds up the release time. At the same time, it reduces the risk of updating, improves the stability of the display layer, and greatly improves the update efficiency.

The embodiment of the present application updates the display layer by means of hot loading, and does not need to restart the web container. In the cluster deployment process, a complicated publishing process such as stopping traffic, restarting the web container, and opening the traffic is not required, thereby greatly improving the simplicity of operation and further improving. Updated efficiency.

When updating the presentation layer, the embodiment of the present application issues an incremental file, and does not need to issue a full amount of the distribution package, which greatly reduces the network resource consumption in the publishing process.

DRAWINGS

Figure 1 is a conventional code merge is an example diagram;

2 is a diagram showing an example of a release of a conventional distribution package;

3 is a flow chart of steps of an embodiment of an update method of a web application according to the present application;

FIG. 4 is a diagram showing an example of publishing a resource update package of the present application; FIG.

FIG. 5 is a structural block diagram of an embodiment of an apparatus for updating a web application according to the present application; FIG.

FIG. 6 is a structural block diagram of an embodiment of an update system for a web application according to the present application.

detailed description

The above described objects, features and advantages of the present application will become more apparent and understood.

For web applications, in order to facilitate development, maintenance, etc., it is necessary to divide the level of web application logic.

The classic MVC framework is generally used to divide the hierarchy. MVC (Model View Controller) separates the input, processing, and output processes of a web application according to the model-view-controller (Controller), and displays the separation using a business logic, data, and interface. The method organizes the code so that a web application can be divided into three layers - the model layer, the view layer, and the control layer.

View (View) represents the user interface. For web applications, it can be summarized as HTML (Hypertext Markup Language) interface, but it may be XHTML (The Extensible Hyper Text Markup Language). ), XML (Extensible Markup Language) and Applet (applet). A web application may have many different views. The processing of the view by the MVC design pattern is limited to the collection and processing of data on the view, as well as the user's request, and does not include the processing of the business process on the view. The processing of the business process is handed over to the Model process. For example, a view of an order only accepts data from the model and displays it to the user, as well as passing input data and requests from the user interface to the control and model.

Model: It is the processing of business processes/states and the formulation of business rules. The processing of the business process is a black box operation for other layers, the model accepts the data requested by the view, and returns the final processing result. The design of the business model can be said to be the main core of MVC. Another important model of the business model is the data model. The data model mainly refers to the data preservation (persistence) of the entity object. For example, save an order to the database, get the order from the database, and can list the model separately, all operations related to the database are limited to the model.

The controller can be understood as receiving a user request, matching the model with the view, and jointly completing the user's request. The role of the division control layer is also obvious, clearly indicating that it is a distributor, what kind of model to choose, what kind of view to choose, what kind of user request can be completed. The control layer does not do any data processing. For example, when a user clicks on a connection, the control layer does not process the business information after accepting the request. It passes the user's information to the model, tells the model what to do, and selects the view that meets the requirements to return to the user. Therefore, one model may correspond to multiple views, and one view may correspond to multiple models.

MVC aggregates business logic into a single component, eliminating the need to rewrite business logic while improving and personalizing the interface and user interaction. MVC has been uniquely developed to map traditional input, processing and output functions in the structure of a logical graphical user interface. MVC tiering also simplifies group development, allowing different developers to develop views, controller logic, and business logic at the same time.

Due to the fast industry characteristics of Internet products, especially the view layer is often modified, there is a very urgent need for the release cycle.

In the traditional publishing process, all code modifications, regardless of whether to modify the view layer or the model layer and the control layer, use the following unified publishing process:

1, modify the code

The developer applies for the branch of the code version management tool (such as subversion, SVN) trunk, modifies the code, and passes the development test process to ensure that the function is correct.

Among them, the trunk can be a relatively stable version of the code, and the branch can be a means of isolating the project. Multiple points can be developed in parallel, and the code is eventually merged into the backbone.

Larger changes to the project can be carried out on the branch, so if the project has problems, does not affect the development of other branches, does not affect the operation of the trunk, the problematic branch can be postponed or even abandoned.

In general, version management tools such as SVN can include trunks, branches, and tags. The usage can be as follows:

Trunk: Can be used for the development of the main direction of the web application. For the development of a new module, you can use trunk. When the module is developed, you need to modify it. You can use branch.

Branch: can be used for parallel development, where parallelism refers to comparison with trunk.

Tag: is used to make a mark, whether it is a release version, but it is a usable version.

For example, the 3.0 version of a web application is developed. At this time, you can make a tag, tag_release_3_0, and then publish based on this tag, such as the installer. Trunk into the 3.1 version of the development, but the 3.0 version found a bug, then you need to do a branch based on tag_release_3_0, branch_bugfix_3_0, based on this branch to modify the vulnerability, wait until the vulnerability is modified, make a tag, tag_release_3_0_1, and then, depending on the need to decide branch_bugfix_3_0 Whether to merge into the trunk.

2, code merge

Combine the code of the branch into the trunk and regression test.

For example, as shown in FIG. 1, when the project development test in branch 1 is completed, after reaching a stable state, branch 1 is merged into the trunk;

The backbone performs integration testing, confirming that a copy of the code from the trunk to the tag is released after the normal release, so the latest branch under the tag is the online stable version of the web application;

At this point, if a project needs a branch, the project can be branched from a stable version of the tag, such as branch 2, for development. When the project development test in branch 2 is completed and a stable state is reached, branch 2 is merged into the trunk.

3, compile

Since the code of the back-end logic (such as Java) is to be compiled, it is necessary to compile the code after the modified trunk.

4, packaging

The compiled file, configuration file, and view code are grouped into a release package to be released. As shown in FIG. 2, the release package generally includes an ear package (ie, App.ear) and Htdocs (host documents).

Among them, the ear package is the code of the model layer and the control layer, including files such as Java and XML.

Htdocs is a folder name, mainly used to put the view layer files, including HTML, vm (template files) and other files.

5, distribution

As shown in Figure 2, the distribution platform publishes the released distribution package to each server in the cluster.

6, deployment

As shown in Figure 2, the application containers of each server (such as jetty, jboss, etc.) are restarted, all resource files are reloaded, and the modified code is posted online, and applied to the web applications of each server, such as Web application 1, Web application 2 ...web application n.

It can be seen that during the entire publishing process, since the model, view, and control are both developed and run as a whole, no matter what code is modified, even if the typo in a copy is modified, it must go through a complicated R&D process, which is completely incompatible with the Internet. The release time requirements of the era.

Moreover, each update requires a full release of the web application (ear package and Htdocs), and the publishing process occupies a large amount of network resources.

During the release process, the application container could not be serviced due to the restart of the application container. Therefore, the cluster release process needs to stop traffic, redeploy, and open traffic with very complicated operations. Since this process does not distinguish whether the business logic is modified or not, the business logic of modifying the Java code is very risky. Each time the redeployment loads all the resource files, including the view layer files and the Java files, the risk of each release is uncontrollable. Stability also has potential risks.

Therefore, one of the core concepts of the embodiments of the present application is creatively proposed, and a new layered publishing idea is proposed, and the back-end code and the presentation layer code are separately released. Since the presentation layer code is light and thin, the changes are frequent, and the online can be released at any time.

Referring to FIG. 3, a flow chart of steps of an embodiment of an update method of a web application according to the present application is shown, which may specifically include the following steps:

Step 301: Receive a resource update file for an independent presentation layer in the web application.

Applying the embodiments of the present application, the web application can be layered based on the layered design idea. The layered design is a common architectural idea in the program development. Since the program code is frequently changed, the layering of the code can simplify the decomposition of the complex problem. Each layer is responsible for its own implementation, and provides a good interface between the service layer and the layer. When changing, only need to care about the changes of one layer, you can not care about other layers.

In this embodiment of the present application, a web application may be divided into at least two layers, where one layer may be a display layer and another layer may be an application layer.

The presentation layer can be used to load the interactive interface in the web application, ie the interface that the user sees and interacts with. A web application may have many different presentation layers. The presentation layer in the embodiment of the present application may be used for collecting and processing data on a view, and processing a user's request, but may not include processing of a business process on the presentation layer. The processing of the business process is handed over to the application layer for processing.

The Internet industry often adjusts the presentation layer content, changes user interactions, copywriting, etc. to enhance the user experience or release new functions. Due to the fast industry characteristics of Internet products, there is a very urgent need for the release cycle. The display layer may include at least one of the following resource files:

Web document HTML, template file vm, image, cascading style sheet CSS (Cascading Style Sheet), script object JS (JavaScript, scripting language) and so on.

Among them, the web page document HTML can mark various parts in the web page to be displayed by using a mark symbol. The web page file itself is a text file. By adding a tag to the text file, you can tell the client (such as a browser) how to display the content (such as how to handle the text, how the screen is arranged, how the image is displayed, etc.).

The template file vm can be a template for developing web applications.

The cascading style sheet CSS can perform pixel-level precise control on the position layout of objects in the webpage, supports almost all font size styles, has the ability to edit webpage objects and model styles, and can perform preliminary interaction design.

The script object JS can be used on an HTML web page to add dynamic functionality to the HTML web page, for example in response to various user actions. The source code does not need to be compiled before being sent to the client (such as a browser). Instead, the text code is sent to the client (such as a browser) and interpreted by the client (such as a browser).

The resource file can be loaded to display the loading time of the interface. When loading, the resource file can have a loading time (that is, a time when the resource file is loaded).

The application layer can be a collection of code in the web application other than the presentation layer, that is, the back-end code in the web application.

If the layering concept of MVC is applied, the application layer can be further divided into a model layer and a control layer.

The model layer can be used for the processing of business processes/states and the formulation of business rules. The layer requests the data and returns the final processing result. The model may include one or more data models, which mainly refer to data preservation (persistence) of the entity objects.

The control layer can receive the request and match the model layer with the presentation layer to complete the request. The control layer clarifies that it is a distributor, what data model to choose, what display layer to choose, and what kind of user request can be completed.

If other layering concepts are applied, the application layer may be further divided into other layers, which is not limited by the embodiment of the present application.

In practical applications, the presentation layer may be independent of the application layer.

Specifically, in the development of the display layer and the application layer, the version management tool (such as SVN) can be used for independent development. The display layer and the application layer can each have an independent trunk. The display layer and the application layer are managed in isolation.

The display layer is relatively thin and light, and can be responsible for simple display logic processing, and the speed is faster; the application layer needs to deal with enterprise-level development, the structure is complex, involving many external resources, transaction-intensive, large amount of data, large number of users, and strong security. Sexual considerations.

At runtime, the presentation layer and the application layer can run in the same web container.

The web container can be a service program, which can be implemented by a web server, and provides a running environment for the web server (such as a JSP server, a servlet server, etc.), so that the web server directly interacts with the environment variable interface in the container, without paying attention to other systems. problem.

The web container can be IIS or PWS including Tomcat in Java, ASP (Active Server Page), and so on.

Traditional view layers typically include partial code for the presentation and application layers. Take the java language as an example, the view layer will have a part of the view processing java code, if this part of the code has to be changed, it is necessary to compile and restart to take effect.

In the embodiment of the present application, if the developer modifies the display layer based on the business requirement, since the presentation layer code is relatively thin and light, the modification is simple, and the workload is small, the code can be modified on the trunk of the display layer to avoid code merge. The traditional release process. Therefore, the configuration management strategy of the presentation layer can be trunk development and trunk release.

Developers modify the code in the trunk, after development, testing, to ensure that the function is correct, generate resources An update file (Htdocs) that can have a modification time to identify when the resource update file was modified.

The resource update file may be an incremental file that is updated for the resource file in the display layer, and may specifically include at least one of the following resource files:

Web document HTML, template file vm, picture, cascading style sheet CSS (Cascading Style Sheet), script object JS (JavaScript, scripting language), etc., that is, which resource file is modified to issue the corresponding resource update file.

Since the back-end code is also managed independently, when updating the independent presentation layer, it is not necessary to compile and package the resource update file, and the resource update file can be directly published.

In the embodiment of the present application, the display layer is independently managed, and when the display layer is updated, the display layer can be directly modified, and the resource update file is released, and the update of the back-end code can be avoided, and the code is not merged, compiled, and packaged. Such complex traditional publishing process greatly reduces the release process and speeds up the release time. At the same time, it reduces the risk of updating, improves the stability of the display layer, and greatly improves the update efficiency.

When updating the presentation layer, the embodiment of the present application issues an incremental file, and does not need to issue a full amount of distribution packages (ear packets and Htdocs), which greatly reduces the network resource consumption in the publishing process.

After the developer completes the resource update file, the developer can distribute the resource update file to one or more servers through the publishing platform to perform the update of the web application display layer installed in the server.

It should be noted that the one or more servers may be cluster servers based on a distributed architecture, and the publishing platform may distribute the resource update files to one or more servers through a distributed version control system (eg, Git).

In a preferred embodiment of the present application, step 302 may include the following sub-steps:

Sub-step S11, storing the resource update file for the independent display layer in the web application into the corresponding directory;

In practical applications, the presentation layer may divide each module according to functions according to the convention, and the resource files in each module are stored in respective corresponding directories.

For example, for the presentation layer of a business website, the directory structure of its resource files can be as follows Show:

The display layer can be divided into three modules in a template file according to functions, namely user (user module), trade (transaction module), and consumeure (transaction record module), and each module has its own corresponding directory. . Among them, user (user module) can be used to load user-related interfaces, such as user login, user registration, help, etc.; trade (transaction module) can be used to load transaction-related interfaces, such as payment, etc.; consumerecord ( The transaction record module) can be used to load the interface of the transaction record. When the server receives the resource update file of the presentation layer, the resource update file needs to be stored in the specified directory, and the original resource file is replaced, so as to perform normal loading and update the display layer.

Sub-step S12, configuring a modification time for the resource update file.

The resource update file generally has a modification time to indicate that the resource update file is last modified. Change the time.

In this embodiment of the present application, the modification time may be a time when the server receives the resource update file.

Step 302, it is determined whether the modification time is greater than or equal to the last load time; if yes, step 303 is performed;

In this practical application, the last load time (ie, the last load time) of each resource file can be stored in the memory of the server.

The embodiment of the present application may modify the framework of the web application, so that the server may scan the resource file periodically or irregularly. If the modification time is greater than or equal to the previous loading time, the version of the resource update file may be considered to be the version of the resource file. To be new, you need to update the resource file.

In the specific implementation, the modification time and the loading time can be converted into seconds to compare the sizes. For example, the modification time is 17:35 on September 29, 2014, and the loading time is 23:42 on September 28, 2014. This time information is larger than the load time.

Step 303: Load the resource update file in the display layer.

Since the resource files are loaded at runtime and placed in memory, they must be reloaded when these resource files are changed. In the embodiment of the present application, if it is determined that the modification time of the resource update file is greater than or equal to the loading time of the last resource file, the resource update file is loaded, and hot loading is implemented.

In a preferred embodiment of the present application, step 303 can include the following sub-steps:

Sub-step S21, starting a template engine corresponding to the display layer;

The presentation layer can be compiled in a fixed template language, and there are many template languages, such as Velocity, JSP (JavaServer Pages), FreeMaker, and so on.

In the case of Velocity, Velocity's template engine can start with Velocity.init() or create a new VelocityEngine class, call the init method in the RuntimeInstance class, and initialize the template engine with the template engine properties set.

Sub-step S22, using the template engine to load a resource update file in the directory.

In a specific implementation, the template resource attribute resourceLoaderPath can be configured in the application to tell the template engine which directory to search for the template file and resource update file of the display layer, such as Config.xml, css.vm, js.vm files.

The web application loads the resource update file distributed to the server, and the modified presentation layer is released online.

The embodiment of the present application updates the display layer by means of hot loading, and does not need to restart the web container. In the cluster deployment process, a complicated publishing process such as stopping traffic, restarting the web container, and opening the traffic is not required, thereby greatly improving the simplicity of operation and further improving. Updated efficiency.

In order to enable a person skilled in the art to better understand the embodiments of the present application, the method for updating the web application in the embodiment of the present application is described below by using specific examples.

As shown in FIG. 4, according to the business requirement, the developer needs to modify the independent display layer in the web application, and needs to add a copy reminder in the payment tool interface of an e-commerce website: “recharge the red envelope”.

The technician can add the copy reminder and provide the code in the web application's resource file i.vm. After the code is tested, a resource update file (Htdocs, ie i.vm) is generated. The technician finds the release list in the publishing platform and determines that only i.vm in a certain directory needs to be released. The distribution platform distributes resource update files (Htdocs, ie, i.vm) to each server through Git, and includes independent applications in web applications (such as Web application 1, Web application 2, ... Web application n) in each server. The layer (App.ear) and the display layer (Htdocs) load the resource update file (Htdocs, i.vm) in the display layer by hot loading, so that the modified presentation layer is released online.

It should be noted that, for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the embodiments of the present application are not limited by the described action sequence, because In accordance with embodiments of the present application, certain steps may be performed in other sequences or concurrently. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required in the embodiments of the present application.

Referring to FIG. 5, a structural block diagram of an embodiment of an update apparatus for a web application according to the present application is shown. Specifically, the following modules may be included:

The resource update file receiving module 501 is configured to receive a resource update file for an independent display layer in the web application; the display layer has a resource file, the resource file has a load time, and the resource update file has a modification time;

The time judging module 502 is configured to determine whether the modification time is greater than or equal to the last loading time; if yes, the resource update file loading module 503 is invoked;

The resource update file loading module 503 is configured to load the resource update file in the display layer.

In a specific implementation, the presentation layer can be used to load an interaction interface in a web application;

The display layer includes at least one of the following resource files:

Web documents, template files, images, cascading style sheets, script objects.

In an actual application, the resource update file is an incremental file that is updated for resource files in the presentation layer.

In a preferred embodiment of the present application, the resource update file receiving module 501 may include the following sub-modules:

a storage submodule, configured to store a resource update file for a separate presentation layer in the web application into a corresponding directory;

The configuration submodule is configured to configure a modification time for the resource update file.

In a preferred embodiment of the present application, the resource update file loading module 503 may include the following sub-modules:

a sub-module, configured to start a template engine corresponding to the display layer;

Loading a sub-module for loading a resource update file in the directory by using the template engine.

In a preferred embodiment of the present application, the web application further includes an application layer, the presentation layer is independent of the application layer, and the presentation layer runs in the same web container as the application layer.

Referring to FIG. 6, a structural block diagram of an embodiment of an update system for a web application according to the present application is shown, and the system may include a publishing platform 610 and one or more servers 620;

The publishing platform 610 can include the following modules:

a resource update file publishing module 611, configured to issue a resource update file for an independent presentation layer in the web application;

The server 620 can include the following modules:

a resource update file receiving module 621, configured to receive a resource update file for an independent display layer in the web application; the display layer has a resource file, the resource file has a load time, and the resource update file has a modification time;

The time judging module 622 is configured to determine whether the modification time is greater than or equal to the last loading time; if yes, the resource update file loading module 623 is invoked;

The resource update file loading module 623 is configured to load the resource update file in the display layer.

In a specific implementation, the presentation layer can be used to load an interaction interface in a web application;

The display layer includes at least one of the following resource files:

Web documents, template files, images, cascading style sheets, script objects.

In an actual application, the resource update file is an incremental file that is updated for resource files in the presentation layer.

In a preferred embodiment of the present application, the resource update file receiving module 621 may include the following sub-modules:

a storage submodule, configured to store a resource update file for a separate presentation layer in the web application into a corresponding directory;

The configuration submodule is configured to configure a modification time for the resource update file.

In a preferred embodiment of the present application, the resource update file loading module 623 may include the following sub-modules:

a sub-module, configured to start a template engine corresponding to the display layer;

Loading a sub-module for loading a resource update file in the directory by using the template engine.

In a preferred embodiment of the present application, the web application further includes an application layer, the presentation layer is independent of the application layer, and the presentation layer runs in the same web container as the application layer.

For the device and the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments can be referred to each other.

Those skilled in the art will appreciate that embodiments of the embodiments of the present application can be provided as a method, apparatus, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

In a typical configuration, the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium. Computer readable media includes both permanent and non-persistent, removable and non-removable media. Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-persistent computer readable media, such as modulated data signals and carrier waves.

The embodiments of the present application refer to a method, a terminal device (system), and a meter according to an embodiment of the present application. A flowchart and/or block diagram of a computer program product is described. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The instruction device implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device such that a series of operational steps are performed on the computer or other programmable terminal device to produce computer-implemented processing, such that the computer or other programmable terminal device The instructions executed above provide steps for implementing the functions specified in one or more blocks of the flowchart or in a block or blocks of the flowchart.

While a preferred embodiment of the embodiments of the present application has been described, those skilled in the art can make further changes and modifications to the embodiments once they are aware of the basic inventive concept. Therefore, the appended claims are intended to be interpreted as including all the modifications and the modifications

Finally, it should also be noted that in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. There is any such actual relationship or order between operations. Furthermore, the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Other elements that are included, or include elements inherent to such a process, method, article, or terminal device. In the absence of more restrictions, elements defined by the phrase "comprising a ..." are not excluded from the process, method, article, or There are additional identical elements in the end device.

The method for updating a web application provided by the present application, a updating device for a web application, and a updating system for a web application are described in detail. In this paper, a specific example is applied to implement the principle and implementation manner of the present application. It is to be noted that the description of the above embodiments is only for helping to understand the method of the present application and its core ideas; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in specific embodiments and applications. In the above, the contents of the present specification should not be construed as limiting the present application.

Claims (11)

A method for updating a web application, comprising: Receiving a resource update file for a separate presentation layer in the web application; the presentation layer has a resource file, the resource file has a load time, and the resource update file has a modification time; Determining whether the modification time is greater than or equal to the last load time; if yes, loading the resource update file in the display layer. The method according to claim 1, wherein the presentation layer is configured to load an interaction interface in a web application; The display layer includes at least one of the following resource files: Web documents, template files, images, cascading style sheets, script objects. The method of claim 1, wherein the resource update file is an incremental file that is updated for resource files in the presentation layer. The method according to claim 1 or 2 or 3, wherein the step of receiving a resource update file for a separate presentation layer in the web application comprises: The resource update file for the independent presentation layer in the web application is stored in the corresponding directory; The modification time is configured for the resource update file. The method according to claim 4, wherein the step of loading the resource update file in the presentation layer comprises: Starting a template engine corresponding to the display layer; The template update engine loads the resource update file in the directory. The method according to claim 1 or 2 or 3 or 5, wherein the web application further comprises an application layer, the presentation layer and the application layer are independent of each other, and the presentation layer and the application layer are Run in the same web container. An update device for a web application, comprising: a resource update file receiving module, configured to receive a resource update file for an independent display layer in the web application; the display layer has a resource file, and the resource file has a loading time, where The resource update file has a modification time; a time judging module, configured to determine whether the modification time is greater than or equal to a previous loading time; if yes, calling a resource update file loading module; a resource update file loading module, configured to load the resource update file in the presentation layer. The device according to claim 7, wherein the presentation layer is used to load an interaction interface in a web application; The display layer includes at least one of the following resource files: Web documents, template files, images, cascading style sheets, script objects. The device according to claim 7 or 8, wherein the resource update file receiving module comprises: a storage submodule, configured to store a resource update file for a separate presentation layer in the web application into a corresponding directory; The configuration submodule is configured to configure a modification time for the resource update file. The device according to claim 9, wherein the resource update file loading module comprises: a sub-module, configured to start a template engine corresponding to the display layer; Loading a sub-module for loading a resource update file in the directory by using the template engine. An update system for a web application, characterized in that the system comprises a publishing platform and one or more servers; The publishing platform includes: a resource update file publishing module, configured to issue a resource update file for an independent presentation layer in the web application; The server includes: a resource update file receiving module, configured to receive a resource update file for an independent presentation layer in the web application; the display layer has a resource file, the resource file has a loading time, and the resource update file has a modification time; a time judging module, configured to determine whether the modification time is greater than or equal to a previous loading time If so, call the resource update file loading module; a resource update file loading module, configured to load the resource update file in the presentation layer.

Images