CN112269622B - Page management method, device, equipment and medium - Google Patents
Page management method, device, equipment and medium Download PDFInfo
- Publication number
- CN112269622B CN112269622B CN202011331635.1A CN202011331635A CN112269622B CN 112269622 B CN112269622 B CN 112269622B CN 202011331635 A CN202011331635 A CN 202011331635A CN 112269622 B CN112269622 B CN 112269622B
- Authority
- CN
- China
- Prior art keywords
- version
- page
- sub
- switched
- management method
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 53
- 238000001514 detection method Methods 0.000 claims abstract description 6
- 230000004044 response Effects 0.000 claims description 26
- 238000000034 method Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 9
- 230000007246 mechanism Effects 0.000 claims description 7
- 230000015654 memory Effects 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000003936 working memory Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure provides a page management method, device, equipment and medium, relates to the field of computers, and particularly relates to a software application technology. The page management method comprises the following steps: storing one or more versions of data and version identifiers thereof corresponding to each sub-page in at least one sub-page; detecting a switching instruction, wherein the switching instruction comprises a version identifier of a target version of a sub-page of a version to be switched in single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched; and responding to the detection of the switching instruction, and switching the current online version of the sub page of the version to be switched into the target version.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a software application technology, and in particular, to a page management method, apparatus, device, and medium.
Background
A single page application is an application that has only one Web page, which loads only a single HTML page, and is able to dynamically rewrite the current page to interact with the user without reloading the entire page. When browsing the single page application, the browsing area can load necessary public resources (HTML, CSS, javaScript and the like) at first, and all the subsequent operations are completed on the single page and controlled by the JavaScript, so that the single page skip is realized, only local resources are refreshed, and the public resources do not need to be repeatedly loaded.
The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, the problems mentioned in this section should not be considered as having been recognized in any prior art unless otherwise indicated.
Disclosure of Invention
According to an aspect of the present disclosure, there is provided a page management method of a single page application including at least one sub page, the page management method including: storing one or more versions of data and version identifiers thereof corresponding to each sub-page in the at least one sub-page; detecting a switching instruction, wherein the switching instruction comprises a version identifier of a target version of a sub-page of a version to be switched in the single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched; and responding to the switching instruction, and switching the current online version of the sub page of the version to be switched to the target version.
According to another aspect of the present disclosure, there is also provided an apparatus including: a storage unit configured to store one or more versions of data corresponding to each of the at least one sub-page and version identifications thereof; the detection unit is configured to detect a switching instruction, wherein the switching instruction comprises a version identifier of a target version of a sub-page of a version to be switched in the single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched; and a switching unit configured to switch a current online version of the sub page of the version to be switched to the target version in response to detecting the switching instruction.
According to another aspect of the present disclosure, there is also provided an electronic apparatus including: a processor; and a memory storing a program comprising instructions that when executed by the processor cause the processor to perform a page management method according to the above.
According to another aspect of the present disclosure, there is also provided a computer readable storage medium storing a program comprising instructions which, when executed by a processor of an electronic device, cause the electronic device to perform a page management method according to the above.
According to another aspect of the present disclosure, there is also provided a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements a page management method according to the above.
According to the technical scheme, one or more historical versions of each sub-page of the single-page application are stored online, and when a version switching instruction is detected, the current online version of the sub-page of the version to be switched is switched to a target version in the one or more historical versions, so that the sub-page of the version to be switched in the single-page application is independently and rapidly switched, and damage can be timely stopped. In addition, when an online problem occurs on a certain sub-page of the single-page application, the page management method can only switch the version of the problem sub-page, and simultaneously continue to present the latest version of other sub-pages, and all the sub-pages are not affected by each other, so that inconvenience brought to a user by frequently changing the plate type and the content of the sub-page can be avoided, and further the use experience of the user can be improved.
Drawings
The accompanying drawings illustrate exemplary embodiments and, together with the description, serve to explain exemplary implementations of the embodiments. The illustrated embodiments are for exemplary purposes only and do not limit the scope of the claims. Throughout the drawings, identical reference numerals designate similar, but not necessarily identical, elements.
FIG. 1 is an application scenario diagram illustrating a page management method according to an example embodiment;
2-3 are flowcharts illustrating a page management method according to an example embodiment;
FIG. 4 is a schematic diagram illustrating a computer configuration platform according to an example embodiment;
FIG. 5 is a schematic diagram illustrating a mobile configuration platform according to an example embodiment;
fig. 6 is a block diagram illustrating a page management apparatus according to an exemplary embodiment; and
FIG. 7 is a block diagram illustrating an exemplary computing device that may be used in connection with the exemplary embodiments.
Detailed Description
In the present disclosure, the use of the terms "first," "second," and the like to describe various elements is not intended to limit the positional relationship, timing relationship, or importance relationship of the elements, unless otherwise indicated, and such terms are merely used to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, they may also refer to different instances based on the description of the context.
The terminology used in the description of the various illustrated examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, the elements may be one or more if the number of the elements is not specifically limited. Furthermore, the term "and/or" as used in this disclosure encompasses any and all possible combinations of the listed items.
In the related art, the existing page management method is to perform page management on the whole single-page application, and when performing a page version switching operation (such as a rollback operation performed after an online problem occurs), the page version switching operation is performed on the whole single-page application. The version switching is performed integrally, so that other normal pages are changed, and the plate type and the content of the frequently changed sub-pages very influence the user experience. In addition, since only the last version exists on the line, the rollback operation can only rollback one version. If the online saved version is still a problematic version, then a rollback to the earlier target version is required, requiring additional time to re-upload the target version's data to the server. In this period, the browsing of the user is still a problem version, so that the use experience of the user is seriously affected, and further the user loss is caused, and even irreparable losses are caused to the product, the brand image and even the company.
In order to solve the technical problems, the method and the device for switching the sub-page of the version to be switched in time can realize the independent and rapid switching of the sub-page of the version to be switched in the single-page application by storing one or more historical versions of each sub-page of the single-page application on line and switching the current on-line version of the sub-page of the version to be switched into a target version in the one or more historical versions when a version switching instruction is detected. In addition, when an online error occurs in a certain sub-page of the single-page application, compared with the method for switching the version of the whole single-page application in the prior art, the page management method can realize that only the version of the problem sub-page is switched, and simultaneously, the latest version of other sub-pages is continuously presented, and all the sub-pages are not affected mutually, so that inconvenience brought to a user by frequently changing the plate type and the content of the sub-page can be avoided, and the use experience of the user can be improved.
Fig. 1 is an application scenario diagram illustrating a page management method according to an exemplary embodiment of the present disclosure. As shown in fig. 1, exemplary application scenarios include a control terminal 1000, a proxy terminal 1100, a content delivery network 1200 (CDN), and a user terminal 1300. Wherein the content delivery network 1200 may comprise a source server 1210 and a plurality of content delivery network nodes 1221-1223 (CDN nodes), the source server 1210 may further be provided with a version switch platform (not shown in the figure) accessible by the control terminal.
Control terminal 1000 can be, for example, but not limited to, an electronic device such as a workstation, desktop computer, laptop computer, tablet computer, etc., an electronic device such as a smart phone with mobile communication capabilities, etc., or any electronic device having HTML5 page browsing capabilities and capable of interacting with HTML5 pages. The control terminal receives the switching request sent by the source station server and judges whether version switching operation is needed or not by the relevant responsible person. If yes, accessing the version switching platform and generating a switching instruction.
Proxy terminal 1100 may be, for example, but not limited to, an electronic device that enables software development for developers of single page applications, such as workstations, desktop computers, laptop computers, and the like that use proxy servers. The proxy terminal sends a data acquisition request of any version of the sub-page of the version to be switched to the source station server or the content distribution network node via the proxy server, and receives the data of the requested version of the sub-page of the version to be switched from the source station server or the content distribution network node. Furthermore, by using the proxy server, the proxy terminal can modify data transmitted from the source station server or the content distribution network node to better perform software development work.
User terminal 1300 may be, for example, but not limited to, an electronic device such as a workstation, desktop computer, laptop computer, tablet computer, personal digital assistant, robot, smart phone, smart home device, car computer, etc., that is capable of browsing and interacting with a single page application. The user terminal sends a data acquisition request for any sub-page to the content distribution network and receives data of the current online version of the page from the content distribution network node.
The proxy terminal may be, for example, a control terminal using a proxy server. The control terminal may be a developer, a non-developer responsible for the single page application, or a terminal device of other related responsible persons, the proxy terminal may be a terminal device of the developer, and the user terminal may be a terminal device of a user using the single page application. It will be appreciated that the foregoing is merely exemplary, and that in a specific software development and operation scenario, different terminal devices may be distinguished in different manners, which are not limited herein.
The content distribution network 1200 is an intelligent virtual network. By placing a layer of intelligent virtual network formed by content distribution network nodes around the network and based on the existing internet, the content distribution network system can redirect the user's request to the content distribution network node nearest to the user in real time according to the network traffic and the comprehensive information of the connection of each node, the load condition, the distance to the user, the response time and the like. The content distribution network can solve the problem of access delay caused by distribution, bandwidth and server performance, and is suitable for scenes such as site acceleration, on-demand, live broadcast and the like. The user can obtain the required content nearby, the congestion condition of the Internet is solved, and the response speed and the success rate of the user for accessing the network resources are improved.
By way of example only, and not by way of limitation,
Source server 1210 may comprise, for example, one or more servers. When a new version is released, the proxy terminal or the control terminal sends the new version data to the source station server, the source station server stores the data, the source station server sends the data to each content distribution network node, and the content distribution network node stores the data, so that the user terminal can acquire the data from the content distribution network node nearest to the user terminal. The source server may store a corresponding version or versions of each sub-page of the single page application, including the current version of each sub-page.
Each content distribution network node 1221-1223 may include, for example, one or more servers and be deployed in a region or network where user access is relatively centralized. As known from the above new version release process, the content distribution network node stores one or more versions corresponding to each sub-page of the single-page application transmitted by the source server, including the current version of each sub-page.
It will be appreciated that the above is merely one exemplary application scenario. In a practical application scenario, the number of content distribution network nodes and user terminals may be only one or a few, or may be huge. The number of control terminals, agent terminals, also varies with the number of relevant principals and developers, and the number of terminals that they can govern. The types and numbers of the source station server, the content distribution network node and the plurality of terminals are not limited in this embodiment.
Fig. 2 is a flowchart illustrating a page management method according to an exemplary embodiment of the present disclosure. As shown in fig. 2, the single page application includes at least one sub-page, and the page management method may include: step S201, storing one or more versions of data corresponding to each sub-page in at least one sub-page and version identification thereof; step S202, detecting a switching instruction; and step S203, responding to the detection of the switching instruction, and switching the current online version of the sub-page of the version to be switched into the target version. Therefore, by storing one or more historical versions of each sub-page of the single-page application on line and switching the current online version of the sub-page of the version to be switched to the target version in the one or more historical versions when the instruction for switching the version is detected, the sub-page of the version to be switched in the single-page application is independently and quickly switched, and damage can be timely stopped. In addition, when an online error occurs in a certain page of the single-page application, compared with the method for switching the version of the whole single-page application in the prior art, the page management method can realize that only the version of the problem sub-page is switched, and simultaneously, the latest version of other sub-pages is continuously presented, and all the sub-pages are not affected mutually, so that inconvenience brought to a user by frequently changing the plate type and the content of the sub-page can be avoided, and the use experience of the user can be improved.
The data of one or more versions corresponding to each sub-page of the single-page application and the version identification thereof can be stored in a source station server or a content distribution network node. Illustratively, as shown in FIG. 1, one or more versions of data corresponding to each sub-page and version identifications thereof may be stored at the source server 1210 and the plurality of content distribution network nodes 1221-1223.
According to some embodiments, the version identification may include a version number of the corresponding sub-page and a stability identification of the sub-page, which may be used to indicate whether the corresponding version of data of the sub-page is stable. The stable identifier can be set by a developer when the version is online, and can be supplemented or modified according to the version operation condition after the version is operated for a period of time. One or more versions of each sub-page stored on the source server or content distribution network node may include versions identified as stable. The stable identifier of the target version of the sub page of the version to be switched can be 'stable', which indicates that the target version is a history stable version, so that when the current version has an online problem, the sub page can be quickly switched to the stable history version by switching to the stable history version.
According to some embodiments, as shown in fig. 3, the page management method may further include: and step S302, sending a switching request to the control terminal in response to the received quantity of the online problem information for the single-page application in unit time exceeding a preset value. Step S301, step S303, and step S305 in fig. 3 are similar to step S101 to step S103 in fig. 2, and other steps in fig. 3 are described later. Therefore, the real-time automatic monitoring of the running condition of the single-page application is realized by counting the number of the on-line problem information which is received in unit time and is aiming at the single-page application, and when the number of the on-line problem information which is received in unit time exceeds a preset value, a switching request is sent to the control terminal, so that a relevant responsible person in charge of the application can be reminded of checking the on-line problem information, and whether to aim at the problem sub-page switching version of the single-page application or not is judged based on the information. By way of example, as shown in fig. 1, control terminal 1000 can include a laptop 1001, a smart phone 1002, and a tablet computer 1003.
According to some embodiments, the online question information may include at least one of the following: the user feeds back information; and at least one of the user terminal, the content distribution network node, and the source station server is each based on internal error information generated by an error reporting mechanism for the single page application. Therefore, by receiving user feedback information from a user and internal error information from a user terminal, a content distribution network node and a source station server, multi-channel supervision on the running condition of the single-page application can be realized, so that when the single-page application has a problem, related responsible persons can obtain richer and more accurate on-line problem information.
The user feedback information may be a problem that the user finds when browsing or using a single page application, such as a display error, a content error, a page logic error, etc., or may be other problems. The user feedback information may be generated by a user feedback module in the single page application in response to the input of the user, or may be generated through a channel outside the single page application, for example, a mail sent by the user to a question feedback mailbox of the application, a call placed to a technical service hotline, and the like, which are not limited herein.
The user terminal, the content distribution network node and the source station server may each include an error reporting mechanism for the single-page application, which may be capable of generating corresponding internal error information according to an abnormal situation of the application occurring during running or a file error of the single-page application. For example, the error reporting mechanism of the user terminal for the single page application may be an error reporting mechanism in an application program running the single page application, and the error reporting mechanism may generate corresponding internal error information when a front-end logic error of the single page application is detected. Error mechanisms such as content delivery network nodes and source station servers can generate corresponding internal error information by monitoring files of single page applications and errors occurring during request-reply requests. It will be appreciated that other means may be employed to generate user feedback information and internal error information associated with a single page application.
The switching request may be a prompt message sent by the source station server to the control terminal, for example, an email, a short message, a system prompt, etc., for informing the relevant responsible person of the single page application of the current abnormal situation of the single page application. The switching request may be an exception prompt that does not contain any specific information, may also include collected online problem information, and may also note which sub-pages currently present an online problem. It can be understood that the main function of the switching request is to prompt the relevant responsible person that the current single page application is abnormal, and the form and the content of the switching request can be specifically set in combination with the actual application scene and the requirement, which is not limited herein.
A switching instruction (specific generation method will be described below) may be generated based on the switching request, and a corresponding sub-page version switching operation is performed based on the switching instruction.
According to some embodiments, step S202, detecting the switch instruction may include: setting a version switching platform; and acquiring a switching instruction generated by the version switching platform. Therefore, by setting the version switching platform capable of generating the switching instruction, the version switching operation can be more conveniently completed.
The version switch platform can be arranged on a source station server and can be directly or indirectly accessed by a control terminal. The control terminal may be configured to access the version switch platform in response to receiving the switch request.
According to some embodiments, the version switch platform may comprise at least one of a computer configuration platform and a mobile configuration platform. Therefore, by setting the computer configuration platform and/or the mobile configuration platform, the related responsible person of the single-page application can be supported to carry out page version switching operation on different terminals, so that a more convenient page management method is realized.
According to some embodiments, the switch instruction may be generated in response to the control terminal performing a related operation by accessing the versioning platform. The switch instruction may include a version identification of a target version of the sub-page of the version to be switched in the single page application, and the target version may be one of the corresponding one or more versions of the stored sub-page of the version to be switched.
According to some embodiments, as shown in fig. 4, computer configuration platform 4000 may include code editing area 4001, wherein the switch instruction is generated in response to modifying a version identification of a currently online version of a sub-page of a version to be switched to a version identification of a target version in the code editing area (see contents in rectangular box 4002 in fig. 4). Therefore, the related responsible person accesses the computer configuration platform through the control terminal and directly modifies the source code of the single-page application in the code editing area of the computer configuration platform, so that the version of the sub-page of the version to be switched is quickly switched based on the computer configuration platform.
According to some embodiments, the mobile configuration platform may be implemented based on HTML5 pages. HTML5 is a language description mode for constructing Web content, and is a new generation standard of the internet. Compared with the last generation of internet standard HTML4, the interaction richness of the HTML5 with the user is remarkably improved. The mobile configuration platform is realized based on the HTML5 page, so that on one hand, the Web advantage of the mobile configuration platform can be reflected, the related responsible person can finish version switching on any mobile device which can browse the HTML5 page and interact with the HTML5 page, the version switching can be finished at the first time when a switching request is received and damage is timely stopped, on the other hand, more convenient version switching operation can be realized through the powerful performance of the HTML5, and more functions of checking on-line problem information and the like can be realized.
According to some embodiments, the mobile configuration platform may include a version identification list of one or more versions included in the sub-page of the version to be switched, wherein the switching instruction is generated in response to selecting a version identification of a target version of the sub-page of the version to be switched from the version identification list. Therefore, by the method, a simple version switching mode on the mobile configuration platform is realized, and therefore, the problem sub-page can be rapidly switched in version through the mobile configuration platform. For example, as shown in fig. 5, the mobile configuration platform 5000 may include an HTML5 page 5001 and include an input/drop-down box 5002 for selecting a sub-page of a version to be switched, an input/drop-down box 5003 for selecting a version of the sub-page, and a version identification list 5004 including one or more versions 5005 of the sub-page.
According to some embodiments, in case of data transmission with the user terminal through the content distribution network node, the content distribution network node may store one or more versions of data corresponding to each of the at least one sub-page and version identification thereof. In this case, the content distribution network node may be controlled to switch the current online version of the sub-page of the version to be switched to the target version in response to detecting the switching instruction. Therefore, the quick loading of the user terminal to the single page application can be realized by using the content distribution network node to carry out data transmission; by storing one or more versions of data including a history stable version of each sub-page at the content distribution network node, the first time when the online problem occurs can be realized, and the current online version of the problem sub-page of the content distribution network node can be switched to the history stable version in response to a switching instruction generated by the control terminal accessing the version switching platform, so that the first time loss is stopped.
According to some embodiments, as shown in fig. 3, the page management method may further include: step S306, in response to receiving the data acquisition request from the user terminal, the target version data of the sub-page of the version to be switched is sent to the user terminal. The data acquisition request comprises an identification of the sub-page of the version to be switched. Therefore, after the version switching is completed, when the user terminal sends a data acquisition request for the sub-page of the version to be switched of the single-page application to the content distribution network node, the content distribution network node sends the data of the switched history stable version (namely the target version) to the user terminal. And after the user terminal sends data acquisition requests for other sub-pages to the content distribution network node, the content distribution network node sends the data of the current online version of the sub-page to the user terminal. Therefore, when a user browses single page application, only the display content of the sub page of the version to be switched is changed back to the historical stable version, the versions of other sub pages are kept unchanged, and all the sub pages are not affected by each other, so that the difference between the plate type and the content brought by the version switching process is reduced to the greatest extent, the use experience of the user is further improved, and the user viscosity is improved. By way of example, as shown in fig. 1, user terminals 1300 may include a laptop 1301, a smartphone 1302, a tablet computer 1303, and a smartwatch 1304, all of which may be in data communication with a content distribution network node 1222.
According to some embodiments, as shown in fig. 3, the page management method may further include: step S304, storing the data of the current online version of the sub page of the version to be switched and the version identification thereof. Therefore, by storing the data of the current online version (namely the problem version) of the sub page, the related responsible person can be helped to quickly reproduce and locate the problem.
According to some embodiments, as shown in fig. 3, the page management method may further include: step S307, in response to receiving the data acquisition request from the proxy terminal, transmits the data of the requested version of the sub-page of the version to be switched to the proxy terminal. The proxy terminal is configured to replace the data of the requested version of the requested sub-page with locally stored debugged data. Therefore, the proxy terminal is used for acquiring the data of the requested version of the sub page of the version to be switched of the single page application, and modifying the data to the adjustable data stored in a text manner, so that the on-line reproduction problem is realized, and the on-line problem can be better debugged and repaired. By way of example, as shown in fig. 1, proxy terminal 1100 may include, for example, a laptop 1101.
It will be appreciated that there is no strict order between step S306 and step S307, and there is no correlation between the user 'S acquisition of the history-stabilized version data and the developer' S acquisition of the data using the agent terminal.
The proxy terminal may have the authority or the capability to obtain data of any version of any sub-page of the single page application stored at the source server or the content distribution network node. Because of the cross-domain problem between the proxy terminal and the source station server or the content distribution network node, the proxy server needs to be used for acquiring the data on the source station server or the content distribution network node. Because the data stored in the source station server and the content distribution network node include the ugly JS and CSS content, and do not include specific logic, the acquired data cannot be directly debugged and the problem can be repaired. Therefore, the proxy server can be used for modifying the content into the unowned JS and CSS content (i.e. debugging data) of the problem version of the problem sub-page stored locally, so that the problem version of the problem sub-page is operated in an online environment, on the one hand, a developer can be helped to quickly locate the problem, and on the other hand, the developer can be helped to find the problem caused by the environment configuration, and the problem cannot be reproduced in the test environment.
According to another aspect of the present disclosure, there is also provided a page management apparatus 600. As shown in fig. 6, the page management apparatus 600 may include a storage unit 601 configured to store data of one or more versions corresponding to each of at least one sub-page and version identification thereof; the detecting unit 602 is configured to detect a switching instruction, where the switching instruction includes a version identifier of a target version of a sub-page of a version to be switched in the single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched; and a switching unit 603 configured to switch the current online version of the sub-page of the version to be switched to the target version in response to detecting the switching instruction.
The operations of the above units 601-603 of the page management device 600 are similar to the steps S201-S203, respectively, and are not repeated here.
According to some embodiments, the detection unit 602 may include: a version switching platform; and the acquisition unit is configured to acquire the switching instruction generated by the version switching platform.
According to another aspect of the present disclosure, there is also provided an electronic device, which may include: a processor; and a memory storing a program comprising instructions that when executed by the processor cause the processor to perform a page management method according to the above.
According to another aspect of the present disclosure, there is also provided a computer readable storage medium storing a program comprising instructions which, when executed by a processor of an electronic device, cause the electronic device to perform a page management method according to the above.
According to another aspect of the present disclosure, there is also provided a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements a page management method according to the above.
With reference to fig. 7, a computing device 7000, which is an example of a hardware device (electronic device) that may be applied to aspects of the disclosure, will now be described. Computing device 7000 may be any machine configured to perform processing and/or computing, which may be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a personal digital assistant, a robot, a smart phone, an on-board computer, or any combination thereof. The page management methods described above may be implemented in whole or at least in part by computing device 7000 or a similar device or system.
The computing device 7000 may include elements that connect with the bus 7002 (possibly via one or more interfaces) or communicate with the bus 7002. For example, computing device 7000 may include a bus 7002, one or more processors 7004, one or more input devices 7006, and one or more output devices 7008. The one or more processors 7004 may be any type of processor and may include, but are not limited to, one or more general purpose processors and/or one or more special purpose processors (e.g., special processing chips). Input device 7006 may be any type of device capable of inputting information to computing device 7000 and may include, but is not limited to, a mouse, keyboard, touch screen, microphone, and/or remote control. Output device 7008 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. The computing device 7000 may also include a non-transitory storage device 7010, or any storage device that is connected to the non-transitory storage device 7010, which may be non-transitory and that may enable data storage, and may include, but is not limited to, a magnetic disk drive, an optical storage device, a solid state memory, a floppy disk, a flexible disk, a hard disk, a magnetic tape, or any other magnetic medium, an optical disk or any other optical medium, a ROM (read only memory), a RAM (random access memory), a cache memory, and/or any other memory chip or cartridge, and/or any other medium from which a computer may read data, instructions, and/or code. The non-transitory storage device 7010 may be detachable from the interface. The non-transitory storage 7010 may have data/programs (including instructions)/code for implementing the methods and steps described above. Computing device 7000 may also include a communication device 7012. The communication device 7012 may be any type of device or system that enables communication with external devices and/or with a network, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset, such as a bluetooth (TM) device, 1302.11 device, wiFi device, wiMax device, cellular communication device, and/or the like.
Computing device 7000 may also include a working memory 7014, which may be any type of working memory that may store programs (including instructions) and/or data useful to the operation of processor 7004, and may include, but is not limited to, random access memory and/or read only memory devices.
The software elements (programs) may reside in the working memory 7014 including, but not limited to, an operating system 7016, one or more application programs 7018, drivers, and/or other data and code. Instructions for performing the above-described methods and steps may be included in one or more applications 7018, and the above-described page management methods may be implemented by instructions of one or more applications 7018 being read and executed by the processor 7004. More specifically, in the above page management method, step S201 to step S203 may be implemented, for example, by the processor 7004 executing the application 7018 having the instructions of step S201 to step S203. Further, other steps in the page management method described above may be implemented, for example, by the processor 7004 executing the application 7018 with instructions to perform the corresponding steps. Executable code or source code of instructions of software elements (programs) may be stored in a non-transitory computer readable storage medium (such as the storage device 7010 described above) and, when executed, may be stored in the working memory 7014 (possibly compiled and/or installed). Executable code or source code for instructions of software elements (programs) may also be downloaded from a remote location.
It should also be understood that various modifications may be made according to specific requirements. For example, custom hardware may also be used, and/or particular elements may be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. For example, some or all of the disclosed methods and apparatus may be implemented by programming hardware (e.g., programmable logic circuits including Field Programmable Gate Arrays (FPGAs) and/or Programmable Logic Arrays (PLAs)) in an assembly language or hardware programming language such as VERILOG, VHDL, c++ using logic and algorithms according to the present disclosure.
It should also be appreciated that the foregoing method may be implemented by a server-client mode. For example, a client may receive data entered by a user and send the data to a server. The client may also receive data input by the user, perform a part of the foregoing processes, and send the processed data to the server. The server may receive data from the client and perform the aforementioned method or another part of the aforementioned method and return the execution result to the client. The client may receive the result of the execution of the method from the server and may present it to the user, for example, via an output device.
It should also be appreciated that the components of computing device 7000 may be distributed across a network. For example, some processes may be performed using one processor while other processes may be performed by another processor remote from the one processor. Other components of computing system 7000 may also be similarly distributed. As such, computing device 7000 may be interpreted as a distributed computing system performing processing at multiple locations.
Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the foregoing methods, systems, and apparatus are merely exemplary embodiments or examples, and that the scope of the present invention is not limited by these embodiments or examples but only by the claims following the grant and their equivalents. Various elements of the embodiments or examples may be omitted or replaced with equivalent elements thereof. Furthermore, the steps may be performed in a different order than described in the present disclosure. Further, various elements of the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced by equivalent elements that appear after the disclosure.
Claims (17)
1. A page management method of a single page application, the single page application including a plurality of sub-pages, the page management method comprising:
controlling a content distribution network node to store data of one or more versions corresponding to each of the plurality of sub-pages and version identifiers thereof, wherein the corresponding one or more versions of each of the plurality of sub-pages comprises a current online version of the sub-page;
Detecting a switching instruction, wherein the switching instruction comprises a version identifier of a target version of a sub-page of a version to be switched in the single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched;
in response to detecting the switching instruction, controlling the content distribution network node to switch the current online version of the sub-page of the version to be switched to the target version;
In response to the content distribution network node receiving a first data acquisition request from a user terminal, controlling the content distribution network node to send the data of the target version of the sub-page of the version to be switched to the user terminal, wherein the data acquisition request comprises an identification of the sub-page of the version to be switched; and
And in response to the content distribution network node receiving a second data acquisition request from a user terminal for other sub-pages in the plurality of sub-pages, controlling the content distribution network node to send the data of the current online version of the other sub-pages to the user terminal.
2. The page management method of claim 1, wherein the detecting a switch instruction comprises:
Setting a version switching platform; and
And acquiring a switching instruction generated by the version switching platform.
3. The page management method of claim 2, wherein the version switch platform comprises at least one of a computer configuration platform and a mobile configuration platform.
4. The page management method of claim 3, wherein said computer configuration platform comprises a code editing area,
Wherein the switch instruction is generated in response to modifying, in the code editing region, a version identification of the currently online version of the sub-page of the version to be switched to a version identification of the target version.
5. A page management method as claimed in claim 3, wherein the mobile configuration platform is implemented based on HTML5 pages.
6. The page management method of claim 5, wherein the mobile configuration platform comprises a version identification list of one or more versions included in the sub-page of the version to be switched,
Wherein the switch instruction is generated in response to selecting a version identification of a target version of the sub-page of the version to be switched from the version identification list.
7. The page management method of claim 2, wherein the switch instruction is generated in response to a control terminal performing a related operation by accessing the version switch platform.
8. The page management method of claim 7, further comprising:
and sending a switching request to the control terminal in response to the quantity of the on-line problem information received in unit time and aiming at the single-page application exceeding a preset value, wherein the control terminal is configured to access a version switching platform in response to the received switching request.
9. The page management method of claim 8, wherein the online question information includes at least one of:
The user feeds back information; and
At least one of the user terminal, the content distribution network node and the source station server is each based on internal error information generated by an error reporting mechanism for the single page application.
10. The page management method of any of claims 1-9, further comprising:
and storing the data of the current online version of the sub page of the version to be switched and the version identification thereof.
11. The page management method of claim 10, further comprising:
And in response to receiving a data acquisition request from a proxy terminal, sending the data of the requested version of the sub-page of the version to be switched to the proxy terminal, wherein the proxy terminal is configured to replace the data of the requested version of the sub-page of the version to be switched with locally stored debugged data of the sub-page of the version to be switched.
12. The page management method according to any one of claims 1-9, wherein the version identification includes a version number of the corresponding sub-page and a stability identification of the sub-page, the stability identification being used to indicate whether the data of the corresponding version of the sub-page is stable.
13. A page management apparatus of a single page application including a plurality of sub pages, the page management apparatus comprising:
A storage unit configured to control a content distribution network node to store data of a corresponding one or more versions of each of the plurality of sub-pages and version identifications thereof, wherein the corresponding one or more versions of each of the plurality of sub-pages includes a current online version of the sub-page;
The detection unit is configured to detect a switching instruction, wherein the switching instruction comprises a version identifier of a target version of a sub-page of a version to be switched in the single-page application, and the target version is one of one or more versions corresponding to the stored sub-page of the version to be switched;
a switching unit configured to control the content distribution network node to switch a current online version of the sub-page of the version to be switched to the target version in response to detecting the switching instruction;
a first sending unit, configured to control the content distribution network node to send the target version data of the sub-page of the version to be switched to the user terminal in response to the content distribution network node receiving a first data acquisition request from the user terminal, where the data acquisition request includes an identification of the sub-page of the version to be switched; and
And the second sending unit is configured to control the content distribution network node to send the data of the current online version of the other sub-pages to the user terminal in response to the content distribution network node receiving a second data acquisition request for the other sub-pages in the plurality of sub-pages from the user terminal.
14. The apparatus of claim 13, wherein the detection unit comprises:
A version switching platform; and
And the acquisition unit is configured to acquire the switching instruction generated by the version switching platform.
15. An electronic device, comprising:
A processor; and
A memory storing a program comprising instructions that when executed by the processor cause the processor to perform the method of any one of claims 1-12.
16. A computer readable storage medium storing a program, the program comprising instructions that when executed by a processor of a computing device cause the computing device to perform the page management method of any of claims 1-12.
17. A computer program product comprising a computer program, wherein the computer program when executed by a processor implements the page management method according to any of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011331635.1A CN112269622B (en) | 2020-11-24 | 2020-11-24 | Page management method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011331635.1A CN112269622B (en) | 2020-11-24 | 2020-11-24 | Page management method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112269622A CN112269622A (en) | 2021-01-26 |
| CN112269622B true CN112269622B (en) | 2024-07-16 |
Family
ID=74339592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011331635.1A Active CN112269622B (en) | 2020-11-24 | 2020-11-24 | Page management method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112269622B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326079A (en) * | 2021-06-24 | 2021-08-31 | 工银科技有限公司 | Service version switching method, switching device, electronic equipment and storage medium |
| CN113781068B (en) * | 2021-09-09 | 2024-05-14 | 平安科技（深圳）有限公司 | Online problem solving method, device, electronic equipment and storage medium |
| CN114924740B (en) * | 2022-04-26 | 2024-07-30 | 江苏康众汽配有限公司 | Active detection method for resource failure in front-end single-page application |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933614A (en) * | 2015-12-30 | 2017-07-07 | 广州爱九游信息技术有限公司 | A kind of single-page application upgrade method and device |
| CN109977026A (en) * | 2019-04-04 | 2019-07-05 | 天津字节跳动科技有限公司 | Test webpage rollback method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11334224B2 (en) * | 2018-03-09 | 2022-05-17 | Optimizely, Inc. | Determining variations of single-page applications |
| US10963230B2 (en) * | 2019-02-14 | 2021-03-30 | International Business Machines Corporation | Single page application continuous integration, build, and deployment |
-
2020
- 2020-11-24 CN CN202011331635.1A patent/CN112269622B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933614A (en) * | 2015-12-30 | 2017-07-07 | 广州爱九游信息技术有限公司 | A kind of single-page application upgrade method and device |
| CN109977026A (en) * | 2019-04-04 | 2019-07-05 | 天津字节跳动科技有限公司 | Test webpage rollback method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112269622A (en) | 2021-01-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112269622B (en) | Page management method, device, equipment and medium | |
| US8601166B2 (en) | Information processing system and information processing method for generating distribution and synchronization rules in a client/server environment based on operation environment data | |
| CN102202061B (en) | Client-server session parallelization | |
| CN107635010B (en) | Traffic scheduling method and device, computer readable storage medium and electronic equipment | |
| US20220413937A1 (en) | Node management method, device and apparatus, storage medium, and system | |
| US10642662B2 (en) | Method for application action synchronization, terminal device, and storage medium | |
| CN112600801A (en) | Flow access control method, equipment and storage medium | |
| CN109922120B (en) | Method and terminal for improving DNS availability | |
| CN116627333A (en) | Log caching method and device, electronic equipment and computer readable storage medium | |
| CN111158654A (en) | Algorithm calling method, device, server and storage medium | |
| CN116301568A (en) | Data access method, device and equipment | |
| CN115996179A (en) | Service node testing method and device, readable medium and electronic equipment | |
| CN108153794B (en) | Page cache data refreshing method, device and system | |
| CN110209964A (en) | A kind of page display method, device and equipment | |
| CN111240998B (en) | Test case processing method and device | |
| US20160330151A1 (en) | Method and system for managing an informational site using a social networking application | |
| CN112954669A (en) | Method, device, network element and storage medium for controlling service of shared terminal | |
| CN113840313B (en) | Network mode control method and device of mobile terminal and computer equipment | |
| CN104516883A (en) | Webpage sharing method, device and system | |
| CN113472638A (en) | Edge gateway control method, system, device, electronic equipment and storage medium | |
| CN115580667A (en) | Data transmission method, device, equipment and storage medium | |
| CN114546961B (en) | File monitoring method, device, medium, equipment and program product | |
| CN114979284B (en) | 5G message scheduling method, device and system | |
| CN114500641B (en) | Message communication method, device and readable medium | |
| CN115038134B (en) | Service request processing method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |