Page obtaining method, device and system
Asynchronous queue-based static page generation on CMS servers addresses server pressure and speed issues, enhancing performance and throughput by generating and uploading static pages efficiently.
Patent Information
- Application Number
- CA3154032
- Authority / Receiving Office
- CA · CA
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-09-10
- Filing Date
- 2020-06-24
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2040-06-24
AI Technical Summary
Existing CMS server page obtaining methods face high pressure and low speed issues, particularly when cache misses occur, leading to inefficient webpage browsing.
A method involving asynchronous queue-based static page generation, where CMS servers send requests to static webpage servers, generating and uploading static pages in an asynchronous queue using resident threads, reducing real-time database queries.
Enhances server performance and page obtaining speed, increasing throughput by over five times and reducing response times to below 200ms, ensuring quasi-real-time static page availability.
Abstract
Description
PAGE OBTAINING METHOD, DEVICE AND SYSTEM BACKGROUND OF THE INVENTION Technical Field
[0001] The present application relates to the field of page obtaining technology, and more particularly to a page obtaining method, a page obtaining device and a page obtaining system.
[0002] Description of Related Art
[0003] There are usually two modes as described below for various CMS servers in the field of webpage content management to obtain page content:
[0004] 1) Page obtainment is first performed in CDN and VARNISH cache servers, when there is no hit of page cache in the CDN and VARNISH cache servers, a back-to-source application directly reads a database to obtain page content. This mode engenders extremely great pressure on the CMS server, makes it difficult to support page accesses of large concurrent volumes, and webpage browsing is rendered low.
[0005] 2) Page obtainment is first performed in CDN and VARNISH cache servers, when there is no hit of page cache in the CDN and VARNISH cache servers, the back-to-source application firstly reads a page update flag, reads the database to obtain page content if there is update, and reads a static page file server if there is no update. In comparison with the first mode, this mode can enhance throughput and webpage browsing speed, but the circumstances of relatively large pressure on the server and noisy response speed are still present when the page is frequently updated.
[0006] Accordingly, there is an urgent need at present to propose a method capable of reducing pressure of the CMS server and enhancing page obtaining speed. SUMMARY OF THE INVENTION
[0007] The present application provides a page obtaining method, a page obtaining device and a page obtaining system, so as to solve prior-art problems in which pressure of the CMS server is large and page obtaining speed is low.
[0008] The present application provides the following solutions.
[0009] According to the first aspect, there is disclosed a page obtaining method that comprises:
[0010] sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0011] extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from a database according to the static page generating request to generate a target static page; and
[0012] uploading the target static page to the static webpage server.
[0013] Preferably, the step of obtaining corresponding page data from a database according to the static page generating request to generate a target static page includes:
[0014] obtaining corresponding page data from the database according to the static page generating request to generate the target static page when a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
[0015] Preferably, the method further comprises:
[0016] sending a target page obtaining request to the database to obtain the target page from the database if there is no static page of the target page in the static webpage server; and
[0017] obtaining the static page if there is the static page of the target page in the static webpage
[0018] Preferably, the method further comprises, prior to sending the static page obtaining request to the static webpage server:
[0019] receiving cache page obtainment failure information from a cache server, wherein the cache page obtainment failure information is generated when the cache server enquires with respect to a cache page obtaining request of a user to find that obtainment of a cache page fails, and the cache page request includes an identification of the target page; and
[0020] the step of sending a static page obtaining request to a static webpage server includes:
[0021] sending a static page obtaining request to the static webpage server according to the cache page obtainment failure information.
[0022] Preferably, the cache server includes a CDN server and / or a VARISH server.
[0023] According to the second aspect, there is further provided a page obtaining method that comprises:
[0024] a CMS server sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0025] the static webpage server enquiring a static page to which the target page corresponds according to the static page obtaining request and returning an enquiring result to the CMS server;
[0026] the CMS server extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from a database according to the static page generating request to generate a target static page; and
[0027] the CMS server uploading to the static webpage server.
[0028] According to the third aspect, there is further provided a page obtaining device that comprises:
[0029] a static page requesting unit, for sending the static page obtaining request to a static webpage server and generating the static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0030] a static page generating unit, for extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from the database according to the static page generating request to generate a target static page; and
[0031] a static page uploading unit, for uploading to the static webpage server.
[0032] Preferably, the static page generating unit is specifically employed for:
[0033] obtaining corresponding page data from the database according to the static page generating request to generate the target static page when a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
[0034] According to the fourth aspect, there is further provided a page obtaining system comprising a CMS server and a static webpage server, of which
[0035] the CMS server is employed for sending a static page obtaining request to the static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from a database according to the static page generating request to generate a target static page to upload to the static webpage server, wherein the static page request includes an identification of the target page; and
[0036] the static webpage server is employed for enquiring a static page to which the target page corresponds according to the static page obtaining request and returning an enquiring result to the CMS server.
[0037] According to the last aspect, there is provided a computer system that comprises:
[0038] one or more processor(s), and
[0039] a memory, associated with the one or more processor(s) and storing a program instruction that performs the following operations when read and executed by the one or more processor(s):
[0040] sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0041] extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from a database according to the static page generating request to generate a target static page; and
[0042] uploading the target static page to the static webpage server.
[0043] According to the specific embodiments provided by the present application, the present application makes public the following technical effects.
[0044] In the technical solutions of the present application, while sending a static page request with respect to a target page to the static webpage server, the CMS server simultaneously generates a static page generating request placed in an asynchronous queue with respect to the target page, processes the static page generating request of the asynchronous queue in a resident asynchronous thread, generates the latest static page and uploads the same to the static webpage server, whereby is realized quick and quasi-real-time generation of static pages, and whereby latest static pages can be obtained by most subsequent page obtaining requests from the static webpage server, and it is not required to read the database in real time in order to obtain page data under most circumstances, so that server performance and page obtaining speed are enhanced in comparison with prior-art technology. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] To more clearly explain the technical solutions in the embodiments of the present application or in the prior-art technology, drawings required for use in the following explanation of the embodiments are briefly described below. Apparently, the drawings described below are merely directed to some embodiments of the present application, while it is further possible for persons ordinarily skilled in the art to base on these drawings to acquire other drawings, and no creative effort will be spent in the process.
[0046] Fig. 1 is a view illustrating the system structure provided by an embodiment of the present application;
[0047] Fig. 2 is a flowchart illustrating the method provided by an embodiment of the present application;
[0048] Fig. 3 is a view illustrating the device structure provided by an embodiment of the present application; and
[0049] Fig. 4 is a view illustrating the computer system architecture provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION
[0050] The technical solutions in the embodiments of the present application are more clearly and comprehensively described below with reference to accompanying drawings in the embodiments of the present application. Apparently, the embodiments as described are merely partial, rather than the entire, embodiments of the present application. Any other embodiments obtainable by persons ordinarily skilled in the art based on the embodiments of the present application shall all fall within the protection scope of the present application.
[0051] The present application aims to provide a novel mode for a CMS server to obtain pages, while sending a static page request with respect to a target page to the static webpage server, the CMS server simultaneously generates a static page generating request placed in an asynchronous queue with respect to the target page, processes the static page generating request in the asynchronous queue by a resident asynchronous thread, generates a latest static page and uploads the same to the static webpage server, whereby the latest static page is stored in the static webpage server, and any page that has once been requested has a corresponding updated static page, so that the CMS server can subsequently obtain updated static pages of most pages at the static webpage server, and it is reduced for the CMS server to request the database in real time for page data so as to solve the problems concerning great pressure and low page obtaining speed. According to statistics, by employing the mode of the present application, system throughput is increased by over five folds, over all TP999 is decreased to below 200ms, and the processing performance of the server is greatly enhanced.
[0052] As shown in Fig. 1, system architecture of the present application includes a CMS server, a cache server, a static webpage server and a database server. When a user browses a page by sending out a page obtaining request, the target page is firstly obtained at the cache server, if there is no corresponding cache page, back-to-source ensues to the CMS server, whereupon the CMS server attempts to obtain the target page from the various servers according to the order of the static webpage server and the database server. That is to say, the static webpage server is requested to obtain a static page; when there is no corresponding static page in the static webpage server, the database server is requested to obtain page data and generate a webpage to return to the user. When the CMS server enquires the static page of the target page at the static webpage server, no matter whether the static page is enquired out or not, the CMS server invariably simultaneously generates the static page generating request with respect to the target page and places the request in an asynchronous queue. A resident asynchronous thread sequentially reads and processes requests of the asynchronous queue, generates the latest static page of the corresponding target page and uploads the same to the static webpage server. Since the request is asynchronous, it is therefore possible to quickly generate the latest static page in quasi- real time, and it is ensured that latest static pages of most pages can be subsequently obtained at the static webpage server.
[0053] For a page still nonexistent in the static webpage server (a page that is requested to be obtained for the first time), the CMS server obtains page data from the database to generate the target page, and returns the same to the user to ensure first round of page obtainment. Since the static page generating request of the page is simultaneously generated in the asynchronous queue, the latest static page of this page is also uploaded to the static webpage server, and it suffices thereafter to only rely on the static webpage server, without having to invoke the database again.
[0054] Embodiment 1
[0055] As shown in Fig. 2, with respect to the aforementioned system, Embodiment 1 of the present application provides a page obtaining method that comprises the following steps.
[0056] S21 - sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page.
[0057] To obtain the target page more quickly, the page obtaining request of the user is usually firstly sent to the cache server for enquiring of the cache page. The cache server includes a CDN server and / or a VARISH server. If there is a corresponding cache page in the cache server, the cache page is directly returned to be displayed to the user; if there is no corresponding cache page, back-to-source ensues to the CMS server to continue for the static page. That is to say, prior to step S21, the method of the present application further comprises:
[0058] S20 - receiving cache page obtainment failure information sent from a cache server. Step S21 is thereafter performed according to the cache enquiring failure information.
[0059] No matter how the requesting result is while the static page is being requested, namely no matter whether the static page exists in the static webpage server or not, the CMS server still generates the static page generating request to be placed in the asynchronous queue.
[0060] With respect to the static page obtaining request, if the target page is requested for the first time, there is no corresponding static page in the static webpage server, in which case it is required to further obtain page data from the database to generate a target page and return the same to the user.
[0061] If the corresponding static page is enquired out of the static webpage server, the page can be directly returned to the user for browsing thereby.
[0062] S22 - extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from the database according to the static page generating request to generate a target static page.
[0063] With respect to asynchronous requests in the asynchronous queue, the resident asynchronous thread processes them, and latest static pages can be quickly generated to be uploaded to the static webpage server. On the basis thereof, the static page of a target page will be stored in the static webpage server as long as the target page has once been requested by the CMS server, so as to facilitate subsequent enquiring of most pages in the static webpage server.
[0064] In this step, if the same user or different users so frequently request(s) the same page that the update frequency of the page is by far exceeded, it can be judged, while the asynchronous request is being processed, whether the target page has already been updated within a period of time, if yes, the asynchronous request is not processed within a preset time, so as to prevent the page from being frequently and repeatedly updated.
[0065] Specifically, it is judged whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition, if it is greater than a certain time, corresponding page data is obtained from the database according to the static page generating request to generate the target static page, if it is smaller than the certain time, processing is temporarily suspended.
[0066] S23 - uploading the target static page to the static webpage server.
[0067] When the CMS server requests next time to obtain the static page of the aforementioned target page, the corresponding static page can be obtained from the static webpage server.
[0068] Embodiment 2
[0069] Corresponding to the method of the aforementioned Embodiment 1, Embodiment 2 of the present application further provides a page obtaining device applied in a CMS server, as shown in Fig. 3, the device comprises the following units.
[0070] A static page requesting unit 31 is employed for sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page.
[0071] To obtain the target page more quickly, the page obtaining request of the user is usually firstly sent to the cache server for enquiring of the cache page. The cache server includes a CDN server and / or a VARISH server. If there is a corresponding cache page in the cache server, the cache page is directly returned to be displayed to the user; if there is no corresponding cache page, back-to-source ensues to the CMS server, and at this time the static page requesting unit 31 of the CMS server sends the static page obtaining request to the static webpage server for obtaining the static page.
[0072] No matter how the requesting result is while the static page is being requested, namely no matter whether the static page exists in the static webpage server or not, the static page requesting unit 31 still generates a static page generating request and places the request in the asynchronous queue.
[0073] With respect to the static page obtaining request, if the target page is requested for the first time, there is no corresponding static page in the static webpage server, in which case the CMS server further includes a target page unit 34 for sending a request to the database to obtain page data to generate a target page for returning to the user.
[0074] If the corresponding static page is enquired out of the static webpage server, the static page requesting unit 31 can directly return the page to the user for browsing thereby.
[0075] A static page generating unit 32 is employed for extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from the database according to the static page generating request to generate a target static page.
[0076] With respect to asynchronous requests in the asynchronous queue, the resident asynchronous thread of the static page generating unit 32 processes them, and latest static pages can be quickly generated to be uploaded through a static page uploading unit 33 to the static webpage server. On the basis thereof, the static page of the target page will be stored in the static webpage server as long as the target page has once been requested by the CMS server, so as to facilitate subsequent enquiring of most pages in the static webpage server.
[0077] In order to prevent the same user or different users from so frequently requesting the same page that the update frequency of the page is by far exceeded and that static pages are frequently generated, the device further comprises a judging unit 35 for judging, while the asynchronous request is being processed, whether the target page has already been updated within a period of time, if yes, the static page generating unit 32 does not process the asynchronous request within a preset time, so as to prevent the page from being frequently and repeatedly updated.
[0078] Specifically, the judging unit 35 judges whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition, if it is greater than a certain time, the static page generating unit 32 obtains corresponding page data from the database according to the static page generating request to generate the target static page, if it is smaller than the certain time, processing is temporarily suspended.
[0079] A static page uploading unit 33 is employed for uploading to the static webpage server.
[0080] Embodiment 3
[0081] With respect to the aforementioned system, Embodiment 3 of the present application provides a page obtaining method that comprises:
[0082] a CMS server sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0083] the static webpage server enquiring the static page to which the target page corresponds according to the static page obtaining request and returning an enquiring result to the CMS server;
[0084] the CMS server extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from the database according to the static page generating request to generate a target static page; and
[0085] the CMS server uploading to the static webpage server.
[0086] Reference can be made to Embodiment 1 for this embodiment, and other sections are no longer described in detail.
[0087] Embodiment 4
[0088] Corresponding to the aforementioned methods and device, Embodiment 4 of the present application provides a computer system that comprises:
[0089] one or more processor(s), and
[0090] a memory, associated with the one or more processor(s) and storing a program instruction that performs the following operations when read and executed by the one or more processor(s):
[0091] sending a static page obtaining request to a static webpage server and generating a static page generating request in an asynchronous queue with respect to a target page, wherein the static page request includes an identification of the target page;
[0092] extracting the static page generating request from the asynchronous queue and obtaining corresponding page data from a database according to the static page generating request to generate a target static page; and
[0093] uploading the target static page to the static webpage server.
[0094] Fig. 4 exemplarily illustrates the framework of the computer system that can specifically include a processor 1510, a video display adapter 1511, a magnetic disk driver 1512, an input / output interface 1513, a network interface 1514, and a memory 1520. The processor 1510, the video display adapter 1511, the magnetic disk driver 1512, the input / output interface 1513, the network interface 1514, and the memory 1520 can be communicably connected with one another via a communication bus 1530.
[0095] The processor 1510 can be embodied as a general CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuit(s) etc. for executing relevant program(s) to realize the technical solutions provided by the present application.
[0096] The memory 1520 can be embodied in such a form as an ROM (Read Only Memory), an RAM (Random Access Memory), a static storage device, or a dynamic storage device etc. The memory 1520 can store an operating system 1521 for controlling the running of a computer system 1500, and a basic input / output system (BIOS) for controlling lower- level operations of the computer system 1500. In addition, the memory 1520 can also store a web browser 1523, a data storage administration system 1524, and an icon font processing system 1525, etc. The icon font processing system 1525 can be an application program that specifically realizes the aforementioned various step operations in the embodiments of the present application. To sum it up, when the technical solutions provided by the present application are to be realized via software or firmware, the relevant program codes are stored in the memory 1520, and invoked and executed by the processor 1510.
[0097] The input / output interface 1513 is employed to connect with an input / output module to realize input and output of information. The input / output module can be equipped in the device as a component part (not shown in the drawings), and can also be externally connected with the device to provide corresponding functions. The input device can include a keyboard, a mouse, a touch screen, a microphone, and various sensors etc., and the output device can include a display screen, a loudspeaker, a vibrator, an indicator light etc.
[0098] The network interface 1514 is employed to connect to a communication module (not shown in the drawings) to realize intercommunication between the current device and other devices. The communication module can realize communication in a wired mode (via USB, network cable, for example) or in a wireless mode (via mobile network, WIFI, Bluetooth, etc.).
[0099] The bus 1530 includes a passageway transmitting information between various component parts of the device (such as the processor 1510, the video display adapter 1511, the magnetic disk driver 1512, the input / output interface 1513, the network interface 1514, and the memory 1520).
[0100] Additionally, the computer system 1500 may further obtain information of specific collection conditions from a virtual resource object collection a condition information database 1541 for judgment on conditions, and so on.
[0101] As should be noted, although merely the processor 1510, the video display adapter 1511, the magnetic disk driver 1512, the input / output interface 1513, the network interface 1514, the memory 1520, and the bus 1530 etc. are illustrated for the aforementioned device, the device may further include other component parts prerequisite for realizing normal running during specific implementation. In addition, as can be understood by persons skilled in the art, the aforementioned device may as well only include component parts necessary for realizing the solutions of the present application, without including the entire component parts as illustrated.
[0102] As can be known through the description to the aforementioned embodiments, it is clearly learnt by person skilled in the art that the present application can be realized through software plus a general hardware platform. Based on such understanding, the technical solutions of the present application, or the contributions made thereby over the state of the art, can be essentially embodied in the form of a software product, and such a computer software product can be stored in a storage medium, such as an ROM / RAM, a magnetic disk, an optical disk etc., and includes plural instructions enabling a computer equipment (such as a personal computer, a cloud server, or a network device etc.) to execute the methods described in various embodiments or some sections of the embodiments of the present application.
[0103] The various embodiments are progressively described in the Description, identical or similar sections among the various embodiments can be inferred from one another, and each embodiment stresses what is different from other embodiments. Particularly, with respect to the system or system embodiment, since it is essentially similar to the method embodiment, its description is relatively simple, and the relevant sections thereof can be inferred from the corresponding sections of the method embodiment. The system or system embodiment as described above is merely exemplary in nature, units therein described as separate parts can be or may not be physically separate, parts displayed as units can be or may not be physical units, that is to say, they can be located in a single site, or distributed over a plurality of network units. It is possible to base on practical requirements to select partial modules or the entire modules to realize the objectives of the embodied solutions. It is understandable and implementable by persons ordinarily skilled in the art without spending creative effort in the process.
[0104] The data processing method, device and equipment provided by the present application are described in detail above, concrete examples are used in this paper to enunciate the principles and modes of execution of the present application, and the descriptions to the above embodiments are merely meant to help understand the method and its essential thinking of the present application; at the same time, persons ordinarily skilled in the art may make various modifications on the specific embodiments and application ranges based on the conception of the present application. In summary, contents of the present Description shall not be understood to restrict the present application.
Claims
1. A system for obtaining a webpage applied in a content management server (CMS) comprising: a static page requesting unit configured to: send a static page obtaining request to a static webpage server; and generate a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; a static page generating unit configured to: extract the static page generating request from the asynchronous queue; obtain corresponding page data from a database according to the static page generating request to generate a static page; and process an asynchronous request within a preset time if the target page has not already been updated within a period of time; a static page uploading unit configured to upload the generated static page to the static webpage server; and a judging unit configured to judge whether the target page has already been updated within the period of time. The system of claim 1 wherein the static page obtaining request is sent to a cache server for enquiring of a cache page.
3. The system of claim 2 wherein the cache server comprises one or more of a CDN server and a varnish server.
4. The system of any one of claims 2 or 3 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed; and wherein if there is no corresponding cache page, back-to-source ensues to the CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
5. The system of any one of claims 1 to 4 further comprising a target page unit configured to send a request to the database to obtain page data to generate the target page.
6. The system of any one of claims 1 to 5 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
7. The system of any one of claims 1 to 6 wherein the judging whether the target page has already been updated within the period of time comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
8. The system of any one of claims 2 to 7 further configured to receive the cache page obtainment failure information sent from the cache server.
9. A method for obtaining a webpage applied in a content management server (CMS) comprising: sending a static page obtaining request to a static webpage server; generating a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; extracting the static page generating request from the asynchronous queue; obtaining corresponding page data from a database according to the static page generating request to generate a static page; processing an asynchronous request within a preset time if the target page has not already been updated within a period of time; uploading the generated static page to the static webpage server; and judging whether the target page has already been updated within the period of time.
10. The method of claim 9 wherein the static page obtaining request is sent to a cache server for enquiring of a cache page.
11. The method of claim 10 wherein the cache server comprises one or more of a CDN server and a varnish server.
12. The method of any one of claims 10 or 11 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed; and wherein if there is no corresponding cache page, back-to-source ensues to the CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
13. The method of any one of claims 9 to 12 further comprising sending a request to the database to obtain page data to generate the target page.
14. The method of any one of claims 9 to 13 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
15. The method of any one of claims 9 to 14 wherein the judging comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
16. The method of any one of claims 10 to 15 further comprising receiving the cache page obtainment failure information sent from the cache server.
17. A computer readable physical memory having stored upon it a computer program for obtaining a webpage, wherein the computer program when executed by a computer is configured to: send a static page obtaining request to a static webpage server; generate a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; extract the static page generating request from the asynchronous queue; obtain corresponding page data from a database according to the static page generating request to generate a static page; process an asynchronous request within a preset time if the target page has not already been updated within a period of time; upload the generated static page to the static webpage server; and judge whether the target page has already been updated within the period of time.
18. The memory of claim 17 wherein the static page obtaining request is sent to a cache server for enquiring of a cache page.
19. The memory of claim 18 wherein the cache server comprises one or more of a CDN server and a varnish server.
20. The memory of any one of claims 18 or 19 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed to a user; and wherein if there is no corresponding cache page, back-to-source ensues to a CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
21. The memory of any one of claims 17 to 20 wherein the computer program is further configured to send a request to the database to obtain page data to generate the target page.
22. The memory of any one of claims 20 to 21 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
23. The memory of any one of claims 17 to 22 wherein the judging comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
24. The memory of any one of claims 18 to 23 wherein the computer program is further configured to receive the cache page obtainment failure information sent from the cache server.
25. A system for obtaining a webpage applied in a content management server (CMS) comprising: a cache server for storing a cache page; a static page requesting unit configured to: send a static page obtaining request to a static webpage server; and generate a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; a static page generating unit configured to: extract the static page generating request from the asynchronous queue; obtain corresponding page data from a database according to the static page generating request to generate a static page; and process an asynchronous request within a preset time if the target page has not already been updated within a period of time; a static page uploading unit configured to upload the generated static page to the static webpage server; and a judging unit configured to judge whether the target page has already been updated within the period of time.
26. The system of claim 25 wherein the static page obtaining request is sent to the cache server for enquiring of the cache page.
27. The system of claim 26 wherein the cache server comprises one or more of a CDN server and a varnish server.
28. The system of any one of claims 25 to 27 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed; and wherein if there is no corresponding cache page, back-to-source ensues to the CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
29. The system of any one of claims 25 to 28 further comprising a target page unit configured to send a request to the database to obtain page data to generate the target page.
30. The system of any one of claims 25 to 29 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
31. The system of any one of claims 25 to 30 wherein the judging whether the target page has already been updated within the period of time comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
32. The system of any one of claims 25 to 31 further configured to receive the cache page obtainment failure information sent from the cache server.
33. A method for obtaining a webpage applied in a content management server (CMS) comprising: storing a cache page in a cache server; sending a static page obtaining request to a static webpage server; generating a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; extracting the static page generating request from the asynchronous queue; obtaining corresponding page data from a database according to the static page generating request to generate a static page; processing an asynchronous request within a preset time if the target page has not already been updated within a period of time; uploading the generated static page to the static webpage server; and judging whether the target page has already been updated within the period of time.
34. The method of claim 33 wherein the static page obtaining request is sent to the cache server for enquiring of the cache page.
35. The method of claim 34 wherein the cache server comprises one or more of a CDN server and a varnish server.
36. The method of any one of claims 33 to 35 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed; and wherein if there is no corresponding cache page, back-to-source ensues to the CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
37. The method of any one of claims 33 to 36 further comprising send a request to the database to obtain page data to generate the target page.
38. The method of any one of claims 33 to 37 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
39. The method of any one of claims 33 to 38 wherein the judging comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
40. The method of any one of claims 33 to 39 further comprising receiving the cache page obtainment failure information sent from the cache server.
41. A computer readable physical memory having stored upon it a computer program for obtaining a webpage, wherein the computer program when executed by a computer is configured to: store a cache page in a cache server; send a static page obtaining request to a static webpage server; generate a static page generating request in an asynchronous queue with respect to a target page, wherein a static page request includes an identification of the target page; extract the static page generating request from the asynchronous queue; obtain corresponding page data from a database according to the static page generating request to generate a static page; process an asynchronous request within a preset time if the target page has not already been updated within a period of time; upload the generated static page to the static webpage server; and judge whether the target page has already been updated within the period of time.
42. The memory of claim 41 wherein the static page obtaining request is sent to the cache server for enquiring of the cache page.
43. The memory of claim 42 wherein the cache server comprises one or more of a CDN server and a varnish server.
44. The memory of any one of claims 41 to 43 wherein if there is the cache page in the cache server, the cache page is directly returned to be displayed; and wherein if there is no corresponding cache page, back-to-source ensues to a CMS, comprising sending the static page obtaining request to the static webpage server for obtaining the static page.
45. The memory of any one of claims 41 to 44 wherein the computer program is further configured to send a request to the database to obtain page data to generate the target page.
46. The memory of any one of claims 44 to 45 wherein the static page of the target page is stored in the static webpage server once the target page has once been requested by the CMS, for facilitating subsequent enquiring of pages in the static webpage server.
47. The memory of any one of claims 41 to 46 wherein the judging comprises judging whether a time difference between a previous static page generating time to which the target page corresponds and a current time satisfies a preset time condition.
48. The memory of any one of claims 41 to 47 wherein the computer program is further configured to receive the cache page obtainment failure information sent from the cache server.
