CN112269622A - Page management method, device, equipment and medium - Google Patents
Page management method, device, equipment and medium Download PDFInfo
- Publication number
- CN112269622A CN112269622A CN202011331635.1A CN202011331635A CN112269622A CN 112269622 A CN112269622 A CN 112269622A CN 202011331635 A CN202011331635 A CN 202011331635A CN 112269622 A CN112269622 A CN 112269622A
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 58
- 238000000034 method Methods 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 9
- 230000007246 mechanism Effects 0.000 claims description 8
- 230000015654 memory Effects 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000001514 detection method Methods 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 230000003936 working memory Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000001133 acceleration 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
Images
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
Abstract
The disclosure provides a page management method, a page management device, page management equipment and a page management medium, which relate to the field of computers, in particular to a software application technology. The page management method comprises the following steps: storing one or more versions of data corresponding to each sub-page in at least one sub-page and version identification thereof; 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 detected 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 technique, and more particularly, to a page management method, apparatus, device, and medium.
Background
A single-page application is an application with only one Web page that loads only a single HTML page and is able to dynamically rewrite the current page to interact with the user without having to reload the entire page. When the single-page application is browsed, the browsing area can load necessary public resources (HTML, CSS, JavaScript and the like) at first, all the operations are completed on the page and are controlled by the JavaScript, so that single-page skipping is realized, only local resources are refreshed, and the public resources do not need to be loaded repeatedly.
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, unless otherwise indicated, the problems mentioned in this section should not be considered as having been acknowledged in any prior art.
Disclosure of Invention
According to an aspect of the present disclosure, there is provided a page management method of a single-page application, the single-page application including at least one sub-page, the page management method including: storing one or more versions of data corresponding to each sub-page in the at least one sub-page and a version identification thereof; 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 detected switching instruction, and switching the current online version of the sub-page of the version to be switched into the target version.
According to another aspect of the present disclosure, there is also provided an apparatus, comprising: the storage unit is configured to store one or more versions of data corresponding to each of the at least one sub-page and a version identifier thereof; a detecting unit, 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 the switching unit is 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.
According to another aspect of the present disclosure, there is also provided an electronic device including: a processor; and a memory storing a program comprising instructions which, when executed by the processor, cause the processor to perform the 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, the program comprising instructions that, when executed by a processor of an electronic device, cause the electronic device to perform the 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 the 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 on line, and when the instruction of switching the versions is detected, the current online version of the sub-page of the version to be switched is switched to the target version of 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 quickly switched, and loss can be timely stopped. In addition, when a certain sub-page of the single-page application has an online problem, the page management method can realize that only the version of the problem sub-page is switched, and simultaneously, the latest versions of other sub-pages are continuously presented, and all sub-pages are not affected with 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 the use experience of the user can be further improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the embodiments and, together with the description, serve to explain the exemplary implementations of the embodiments. The illustrated embodiments are for purposes of illustration only and do not limit the scope of the claims. Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.
FIG. 1 is an application scenario diagram illustrating a page management method according to an exemplary embodiment;
2-3 are flowcharts illustrating a page management method according to an exemplary embodiment;
FIG. 4 is a schematic diagram illustrating a computer configuration platform in accordance with an illustrative embodiment;
FIG. 5 is a schematic diagram illustrating a mobile configuration platform according to an exemplary embodiment;
FIG. 6 is a block diagram illustrating a page management apparatus according to an exemplary embodiment; and
fig. 7 is a block diagram showing an exemplary computing device to which the exemplary embodiments can be applied.
Detailed Description
In the present disclosure, unless otherwise specified, the use of the terms "first", "second", etc. to describe various elements is not intended to limit the positional relationship, the timing relationship, or the importance relationship of the elements, and such terms are used only 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, based on the context, they may also refer to different instances.
The terminology used in the description of the various described 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, if the number of elements is not specifically limited, the elements may be one or more. Furthermore, the term "and/or" as used in this disclosure is intended to encompass any and all possible combinations of the listed items.
In the related art, the conventional page management method is to perform page management on the whole single-page application, and when a page version switching operation (for example, a rollback operation performed after an online problem occurs) is performed, the page version switching is performed on the whole single-page application. And the overall version switching can cause other normal pages to change, and the frequent change of the plate type and the content of the sub-page can 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 saved version on the line is still the problematic version, it needs to be rolled back to the earlier target version, requiring additional time to re-upload the target version's data to the server. During this time, the user still browses the problem version, which seriously affects the user experience, and further causes the user to lose, even irreparable loss of products, brand images, and even companies.
In order to solve the technical problem, according to the method and the device, one or more historical versions of each sub-page of the single-page application are stored on line, and when an instruction for switching the versions is detected, the current online version of the sub-page of the version to be switched is switched to the target version of 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 quickly switched, and loss can be timely stopped. In addition, when an online error occurs in a certain sub-page of the single-page application, compared with a 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 versions of other sub-pages are continuously presented, and the sub-pages are not affected with 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 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, an exemplary application scenario includes a control terminal 1000, a proxy terminal 1100, a content delivery network 1200(CDN), and a user terminal 1300. The content distribution network 1200 may include a source station server 1210 and a plurality of content distribution network nodes 1221 and 1223(CDN nodes), and the source station server 1210 may further include a version switching platform (not shown in the figure) accessible by the control terminal.
The control terminal 1000 can be, for example and without limitation, an electronic device such as a workstation, a desktop computer, a laptop computer, a tablet computer, and the like, an electronic device such as a smart phone with a mobile communication function, or any electronic device with an HTML5 page browsing function and capable of interacting with an HTML5 page. The control terminal receives the switching request sent by the source station server, and the related responsible person judges whether the version switching operation is needed. And if so, accessing the version switching platform and generating a switching instruction.
The proxy terminal 1100 may be, for example, but not limited to, an electronic device for software development by a developer of a single-page application, such as a workstation using a proxy server, a desktop computer, a laptop computer, or the like. 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 through the proxy server, and receives 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 sent from the source station server or the content distribution network node to better perform software development work.
The 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, in-vehicle computer, etc., that allows a user to browse and interact 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 can be terminal equipment of developers, non-developers in charge of the single-page application and other related responsible persons, the agent terminal can be terminal equipment of the developers, and the user terminal can be terminal equipment of users using the single-page application. It is to be understood that the above is only an exemplary distinction, and in a specific software development and operation scenario, different terminal devices may be distinguished in different ways, and are not limited herein.
The content distribution network 1200 is an intelligent virtual network. By placing a layer of intelligent virtual network on the basis of the existing internet, which is formed by content distribution network nodes at various positions of the network, the content distribution network system can redirect the request of a user to the content distribution network node closest to the user in real time according to network flow, connection of each node, load condition, distance to the user, response time and other comprehensive information. 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 broadcasting, live broadcasting and the like. The user can obtain the required content nearby, the crowded condition of the internet is solved, and the response speed and the success rate of the user for accessing the network resources are improved.
In an exemplary manner, the first and second electrodes are,
the source station server 1210 may include, for example, one or more servers. For example, 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 new version data to each content distribution network node, and the content distribution network node stores the data, so that the user terminal can obtain the data from the content distribution network node closest to the user terminal. The source site server may store one or more versions of each sub-page of the single-page application, including a current version of each sub-page.
Each of the content distribution network nodes 1221-1223 may comprise, for example, one or more servers and be deployed in a region or network where user access is relatively centralized. As known from the new version publishing process, the content distribution network node stores one or more versions of each sub-page of the single-page application sent by the source station server, including the current version of each sub-page.
It will be appreciated that the above is only 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 very large. The number of control terminals, agent terminals also varies with the number of associated principals and developers and the number of terminals they may possess. In this embodiment, the types and the numbers of the source station server, the content distribution network node, and the various terminals are not limited.
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 and version identification thereof corresponding to each sub page in at least one sub page; step S202, detecting a switching instruction; and step S203, responding to the detected switching instruction, and switching the current online version of the sub-page of the version to be switched into the target version. Therefore, one or more historical versions of each sub-page of the single-page application are stored on line, and when the instruction of switching the versions is detected, the current online version of the sub-page of the version to be switched is switched to the target version of 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 quickly switched, and the loss 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 versions of other sub-pages are continuously presented, and the sub-pages are not affected with 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 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 the source station server or the content distribution network node. For example, as shown in fig. 1, the source server 1210 and the plurality of content distribution network nodes 1221 and 1223 may each store one or more versions of data corresponding to each sub-page and a version identifier thereof.
According to some embodiments, the version identification may include a version number of the corresponding sub-page and a stable identification of the sub-page, and the stable identification may be used to indicate whether data of the corresponding version of the sub-page is stable. The stable mark can be set by a developer when the version is on line, and can also be supplemented or modified according to the version running condition after the version runs for a period of time. The one or more versions of each sub-page stored on the source site server or content distribution network node may include a version that is stably identified as "stable". The stable mark 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 historical stable version, so that when the current version has an online problem, the sub-page can be switched to the stable historical version quickly by switching to the stable historical version.
According to some embodiments, as shown in fig. 3, the page management method may further include: step S302, responding to the fact that the quantity of the on-line problem information aiming at the single-page application received in unit time exceeds a preset value, and sending a switching request to the control terminal. Steps S301, S303, and S305 in fig. 3 are similar to steps S101 to S103 in fig. 2, and other steps in fig. 3 are described later. Therefore, real-time automatic monitoring of the running condition of the single-page application is achieved by counting the quantity of the on-line problem information received in unit time aiming at the single-page application, and when the quantity of the on-line problem information received in unit time exceeds a preset value, a switching request is sent to the control terminal, so that a relevant person in charge of the application can be reminded to check the on-line problem information, and whether the version is required to be switched aiming at the problem sub-page of the single-page application or not is judged based on the information. Illustratively, as shown in fig. 1, the control terminal 1000 can include a laptop computer 1001, a smartphone 1002, and a tablet computer 1003.
According to some embodiments, the online issue information may include at least one of: user feedback information; and internal error information generated by at least one of the user terminal, the content distribution network node and the source station server based on 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 found by the user when browsing or using the single page application, such as a display error, a content error, a page logic error, and the like, or other problems. The user feedback information may be generated by a user feedback module in the single-page application in response to an input of the user, or may be generated through a channel outside the single-page application, such as an email sent by the user to a problem feedback mailbox of the application, a telephone call made to a technical service hotline, and the like, which is not limited herein.
The user terminal, the content distribution network node and the source station server can respectively comprise error reporting mechanisms aiming at the single-page application, and the error reporting mechanisms can generate corresponding internal error information according to abnormal conditions occurring in the operation of the application or file errors 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 reporting mechanisms, such as content distribution network nodes and source station servers, may generate corresponding internal error information by monitoring for errors that occur during file and request-reply requests of a single-page application. It will be appreciated that other means of generating user feedback information and internal error information related to a single-page application may also be employed.
The switching request may be prompt information sent by the source station server to the control terminal, such as an email, a short message, a system prompt, and the like, for notifying a relevant person in charge of the single-page application of a current abnormal condition 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 indicate which sub-pages have online problems currently. It can be understood that the main role of the switching request is to prompt the relevant responsible person that the current single-page application is abnormal, and the form and content of the switching request may be specifically set in combination with the actual application scenario and requirements, which is not limited herein.
A switching instruction may be generated based on the switching request (a specific generation method will be described in the following), and a corresponding sub-page version switching operation may be performed based on the switching instruction.
According to some embodiments, the step S202 of detecting the switching instruction may include: setting a version switching platform; and acquiring a switching instruction generated by the version switching platform. Therefore, the version switching platform capable of generating the switching instruction is arranged, so that the version switching work can be completed more conveniently.
The version switching platform can be arranged on the source station server and can be directly or indirectly accessed by the control terminal. The control terminal may be configured to access the version switching platform in response to receiving a switch request.
According to some embodiments, the version-switching platform may include 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 method can support the relevant responsible person of the single-page application to carry out page version switching operation at different terminals, thereby realizing a more convenient page management method.
According to some embodiments, the switching instruction may be generated in response to the control terminal performing the relevant operation by accessing the version switching platform. The switching 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 one or more versions corresponding to the stored sub-page of the version to be switched.
According to some embodiments, as shown in fig. 4, computer configuration platform 4000 may comprise a code editing area 4001, wherein the switching instruction is generated in response to modifying a version identifier of a currently online version of the sub-page of the version to be switched to a version identifier of the target version (see contents in rectangular block 4002 in fig. 4) in the code editing area. Therefore, related responsible persons access the computer configuration platform through the control terminal and directly modify the source code of the single-page application in the code editing area of the computer configuration platform, and therefore the version of the sub-page 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 way to build Web content, and is a new generation standard of the internet. Compared with the previous generation 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, on one hand, the Web advantages can be embodied, so that a related person in charge can complete version switching on any mobile device which can browse the HTML5 page and can interact with the HTML5 page, the version switching can be completed at the first time when a switching request is received, loss can be stopped in time, on the other hand, more convenient version switching operation can be realized through the strong performance of the HTML5, and more functions such as checking on-line problem information can be realized.
According to some embodiments, the mobile configuration platform may comprise a version identification list of one or more versions comprised by the sub page of the version to be switched, wherein the switching instruction is generated in response to selecting the version identification of the target version of the sub page of the version to be switched from the version identification list. Therefore, through the mode, a simple version switching mode on the mobile configuration platform is realized, and therefore the problem sub-page can be quickly switched 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 enter/drop-down box 5002 for selecting a sub-page of which a version is to be switched, an enter/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 the case of data transmission with a user terminal through a content distribution network node, the content distribution network node may store one or more versions of data corresponding to each of at least one sub-page and a 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 rapid loading of the single-page application by the user terminal can be realized by using the content distribution network node for data transmission; and by storing the data of one or more versions including the historical stable version of each sub-page in the content distribution network node, the problem that the current online version of the problem sub-page of the content distribution network node is switched to the historical stable version at the first time when the online problem occurs can be realized in response to a switching instruction generated by the control terminal accessing the version switching platform, so that the loss can be stopped at the first time.
According to some embodiments, as shown in fig. 3, the page management method may further include: step S306, responding to the received data acquisition request from the user terminal, and sending the data of the target version of the sub-page of the version to be switched to the user terminal. The data acquisition request comprises the identification of the sub-page of the version to be switched. Therefore, after the version switching is completed, after 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 switched data of the history stable version (namely the target version) to the user terminal. And after the user terminal sends a data acquisition request aiming at 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 the 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 the sub-pages are not affected with each other, so that the difference between the plate type and the content brought by the version switching process is reduced to the maximum extent, the use experience of the user is improved, and the viscosity of the user is improved. Illustratively, as shown in fig. 1, a user terminal 1300 may include a laptop computer 1301, a smart phone 1302, a tablet computer 1303 and a smart watch 1304, which may each 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: and S304, storing the data of the current online version of the sub-page of the version to be switched and the version identification thereof. Thus, by storing data for the current online version of the sub-page (i.e., the problem version), the relevant principal 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, responding to the received data acquisition request from the proxy terminal, and sending 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 requested version of data of the requested sub-page with locally stored debuggable data. Therefore, the data of the requested version of the sub-page to be converted of the single-page application is obtained by using the proxy terminal, and the data is modified by locally stored adjustable data, so that the problem of online reproduction is solved, and the online problem can be better debugged and repaired. Illustratively, as shown in FIG. 1, the proxy terminal 1100 may comprise, for example, a laptop 1101.
It is understood that there is no strict order between step S306 and step S307, and there is no correlation between the user acquiring the history stable version data and the developer acquiring the data using the agent terminal.
The proxy terminal may have the authority or ability to obtain any version of data of any sub-page of the single-page application stored at the source station server or content distribution network node. Because the cross-domain problem exists between the proxy terminal itself and the source station server or the content distribution network node, the proxy server needs to be used to acquire data on the source station server or the content distribution network node. Because the data stored on the source station server and the content distribution network node comprises the defaulted JS and CSS content and does not comprise specific logic, the acquired data cannot be directly debugged and the problem cannot be repaired. Therefore, the proxy server can be used for modifying the contents into unburnt JS and CSS contents (namely debuggable data) of the problem version of the problem sub-page stored locally, so that the problem version of the problem sub-page is operated on line in an environment, and therefore on one hand, the problem can be rapidly positioned by developers, on the other hand, the problems caused by environment configuration can be found by the developers, and the problems can not be reproduced in a test environment.
According to another aspect of the present disclosure, a page management apparatus 600 is also provided. As shown in fig. 6, the page management apparatus 600 may include a storage unit 601 configured to store one or more versions of data corresponding to each of at least one sub-page and a version identifier thereof; a detecting unit 602, 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 a 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, in response to detecting the switching instruction, the current online version of the sub-page of the version to be switched to the target version.
The operations of the units 601 and 603 of the page management device 600 are similar to those of the steps S201 to S203, and are not described herein again.
According to some embodiments, the detection unit 602 may comprise: 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 which, when executed by the processor, cause the processor to perform the 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, the program comprising instructions that, when executed by a processor of an electronic device, cause the electronic device to perform the 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 the page management method according to the above.
Referring to fig. 7, a computing device 7000, which is an example of a hardware device (electronic device) to which aspects of the present disclosure may be applied, will now be described. Computing device 7000 may be any machine configured to perform processing and/or computing, and 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 above-described page management methods may be implemented, in whole or at least in part, by computing device 7000 or similar devices or systems.
Software elements (programs) may be located 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 application programs 7018, and the above-described page management methods may be implemented by instructions for reading and executing the one or more application programs 7018 by the processor 7004. More specifically, in the above-described page management method, steps S201 to S203 can be realized, for example, by the processor 7004 executing the application 7018 having the instructions of steps S201 to S203. Further, other steps in the above-described page management method may be implemented, for example, by the processor 7004 executing the application 7018 with instructions in executing the respective steps. Executable code or source code of instructions of the 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 the instructions of the software elements (programs) may also be downloaded from a remote location.
It will also be appreciated that various modifications may be made in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might 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 circuitry 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 understood that the foregoing method may be implemented in a server-client mode. For example, a client may receive data input by a user and send the data to a server. The client may also receive data input by the user, perform part of the processing in the foregoing method, and transmit the data obtained by the processing 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 results of the execution to the client. The client may receive the results of the execution of the method from the server and may present them to the user, for example, through an output device.
It should also be understood 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 that is remote from the one processor. Other components of computing system 7000 may also be similarly distributed. Thus, computing device 7000 may be construed as a distributed computing system performing the processes 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 above-described 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 as issued and their equivalents. Various elements in the embodiments or examples may be omitted or may be replaced with equivalents thereof. Further, the steps may be performed in an order different from that described in the present disclosure. Further, various elements in 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 with equivalent elements that appear after the present disclosure.
Claims (19)
1. A page management method of a single-page application, the single-page application including at least one sub-page, the page management method comprising:
storing one or more versions of data corresponding to each sub-page in the at least one sub-page and a version identification thereof;
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
and responding to the detected switching instruction, and switching the current online version of the sub-page of the version to be switched into the target version.
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 the computer configuration platform includes a code editing area,
wherein the switching instruction is generated in response to modifying the version identifier of the current online version of the sub-page of the version to be switched to the version identifier of the target version in the code editing area.
5. The page management method of claim 3 wherein said mobile configuration platform is implemented based on HTML5 pages.
6. The page management method of claim 5, wherein the mobile configuration platform includes 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 the version identifier of the target version of the sub-page of the version to be switched from the version identifier list.
7. The page management method of claim 2, wherein the switching instruction is generated in response to a control terminal performing a related operation by accessing the version switching platform.
8. The page management method of claim 7, further comprising:
and in response to the quantity of the on-line problem information received in unit time aiming at the single-page application exceeding a preset value, sending a switching request to the control terminal, wherein the control terminal is configured to access a version switching platform in response to receiving the switching request.
9. The page management method of claim 8, wherein the online issue information comprises at least one of:
user feedback information; and
at least one of the user terminal, the content distribution network node and the source station server each generate internal error information based on 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:
responding to a data acquisition request received from an agent terminal, and sending the data of the requested version of the sub-page of the version to be switched to the agent terminal, wherein the agent terminal is configured to replace the data of the requested version of the sub-page of the version to be switched with the debuggable data of the locally stored sub-page of the version to be switched.
12. The page management method according to any one of claims 1 to 9, wherein the version identification includes a version number of the corresponding sub-page and a stable identification of the sub-page, and the stable identification is used to indicate whether data of the corresponding version of the sub-page is stable.
13. The page management method according to claim 1, wherein the data transmission is performed with the user terminal through a content distribution network node, the content distribution network node stores one or more versions of data corresponding to each of the at least one sub-page and a version identification thereof,
wherein, in response to detecting the switching instruction, the content distribution network node is controlled to switch the current online version of the sub-page of the version to be switched to the target version.
14. The page management method of claim 1 or 13, further comprising:
and responding to a data acquisition request from a user terminal, and sending 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 the identifier of the sub-page of the version to be switched.
15. A page management apparatus of a single-page application, the single-page application including at least one sub-page, the page management apparatus comprising:
the storage unit is configured to store one or more versions of data corresponding to each of the at least one sub-page and a version identifier thereof;
a detecting unit, 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
and the switching unit is 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.
16. The apparatus of claim 15, 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.
17. 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 of claims 1-14.
18. 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-14.
19. 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-14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011331635.1A CN112269622A (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 CN112269622A (en) | 2020-11-24 | 2020-11-24 | Page management method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112269622A true CN112269622A (en) | 2021-01-26 |
Family
ID=74339592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011331635.1A Pending CN112269622A (en) | 2020-11-24 | 2020-11-24 | Page management method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112269622A (en) |
Cited By (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 |
| CN113781068A (en) * | 2021-09-09 | 2021-12-10 | 平安科技（深圳）有限公司 | Online problem solving method and device, electronic equipment and storage medium |
| CN113781068B (en) * | 2021-09-09 | 2024-05-14 | 平安科技（深圳）有限公司 | Online problem solving method, device, electronic equipment and storage medium |
Citations (4)
| 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 |
| US20190278438A1 (en) * | 2018-03-09 | 2019-09-12 | Optimizely, Inc. | Determining Variations of Single-Page Applications |
| US20200264848A1 (en) * | 2019-02-14 | 2020-08-20 | International Business Machines Corporation | Single page application continuous integration, build, and deployment |
-
2020
- 2020-11-24 CN CN202011331635.1A patent/CN112269622A/en active Pending
Patent Citations (4)
| 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 |
| US20190278438A1 (en) * | 2018-03-09 | 2019-09-12 | Optimizely, Inc. | Determining Variations of Single-Page Applications |
| US20200264848A1 (en) * | 2019-02-14 | 2020-08-20 | International Business Machines Corporation | Single page application continuous integration, build, and deployment |
| CN109977026A (en) * | 2019-04-04 | 2019-07-05 | 天津字节跳动科技有限公司 | Test webpage rollback method and device |
Cited By (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 |
| CN113781068A (en) * | 2021-09-09 | 2021-12-10 | 平安科技（深圳）有限公司 | Online problem solving method and device, electronic equipment and storage medium |
| CN113781068B (en) * | 2021-09-09 | 2024-05-14 | 平安科技（深圳）有限公司 | Online problem solving method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102565360B1 (en) | Method and device for testing map service | |
| CN110971655B (en) | Offline client playback and synchronization | |
| CN110162512B (en) | Log retrieval method, device and storage medium | |
| CN110795311B (en) | Event playback method and device | |
| EP4071609A1 (en) | Node management method, device and apparatus, storage medium, and system | |
| CN112256676A (en) | Method, device, equipment and medium for migrating database | |
| CN110781149A (en) | Method, device, equipment and storage medium for managing live broadcast room information | |
| CN111475754B (en) | Page loading method, device, terminal and storage medium | |
| CN104919448A (en) | Device, method and system for displaying digital editions | |
| CN116627333A (en) | Log caching method and device, electronic equipment and computer readable storage medium | |
| US10432490B2 (en) | Monitoring single content page application transitions | |
| CN112269622A (en) | Page management method, device, equipment and medium | |
| CN107102937B (en) | User interface testing method and device | |
| CN110209964A (en) | A kind of page display method, device and equipment | |
| CN111625344B (en) | Resource scheduling system, method and device in application system | |
| WO2023179183A1 (en) | Subprogram synchronization processing | |
| CN111159033A (en) | Software testing method and device | |
| CN113840313B (en) | Network mode control method and device of mobile terminal and computer equipment | |
| CN111143526B (en) | Method and device for generating and controlling configuration information of counsel service control | |
| CN113626402A (en) | Log data acquisition method and device, electronic equipment and storage medium | |
| CN113297515A (en) | Resource information processing method and device, computer storage medium and electronic equipment | |
| CN104516883A (en) | Webpage sharing method, device and system | |
| CN113472638A (en) | Edge gateway control method, system, device, electronic equipment and storage medium | |
| CN112433891A (en) | Data processing method and device and server | |
| CN111158654A (en) | Algorithm calling method, device, server and storage 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 |