CN117932186A - Page instance management method, device, computer equipment and storage medium - Google Patents
Page instance management method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN117932186A CN117932186A CN202410187237.9A CN202410187237A CN117932186A CN 117932186 A CN117932186 A CN 117932186A CN 202410187237 A CN202410187237 A CN 202410187237A CN 117932186 A CN117932186 A CN 117932186A
- Authority
- CN
- China
- Prior art keywords
- route
- target
- historical
- data
- instance
- 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 abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 57
- 238000013138 pruning Methods 0.000 claims abstract description 23
- 238000004590 computer program Methods 0.000 claims description 40
- 238000012217 deletion Methods 0.000 claims description 29
- 230000037430 deletion Effects 0.000 claims description 29
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000009877 rendering Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a page instance management method, a page instance management device, computer equipment and a storage medium. The method comprises the following steps: acquiring historical route data and historical instance data of a target application; according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data; and according to the reference route, performing instance pruning on the historical instance data to obtain target instance data. According to the method and the device, the historical instance data is deleted by referring to the route, so that compared with the operation of caching all page instances in the prior art, the method and the device can effectively reduce the page memory of the target application and prevent the page memory from exceeding the threshold value, thereby influencing the normal operation of the target application.
Description
Technical Field
The present application relates to the field of artificial intelligence technologies, and in particular, to a method and apparatus for managing page instances, a computer device, and a storage medium.
Background
At present, along with the increasing general and standard of WEB standards (webpage standards), the difference between different browsers is also smaller, the development of front-end technology is mature, and single-page application becomes a type of selection for the research and development of a plurality of B/S (Browser/Server) applications.
In the conventional technology, in order to prevent data loss caused by single page application when page switching is performed and ensure page rendering efficiency, all page instances can be cached, so that when a rendered page is triggered for the second time, page rendering operation does not need to be performed again.
However, when the method is adopted to cache all page instances, the condition of overlarge page memory can occur, and the normal operation of single page application is affected.
Disclosure of Invention
Based on this, it is necessary to provide a page instance management method, device, computer equipment and storage medium capable of reducing page memory and ensuring normal operation of single page application, aiming at the technical problems.
In a first aspect, the present application provides a method for managing a page instance. The method comprises the following steps:
acquiring historical route data and historical instance data of a target application;
According to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with recording time earlier than the target recording time from the historical route data;
And according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
In one embodiment, the selecting, according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, the reference route with the recording time earlier than the target recording time from the historical route data includes:
determining a route index identifier from the historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route;
And selecting a reference route from the historical route data according to the route index identification.
In one embodiment, the determining, according to the target route of the page to be displayed in the target application and the target record time of the target route, the route index identifier from the historical route data includes:
verifying whether the historical route data contains the target route;
if so, the position of the target route in the historical route data is used as a route index identification;
if not, carrying out data update on the historical route data according to the target record time of the target route; and adding the target route into the updated historical route data, and using the adding position of the target route in the updated historical route data as a route index identification.
In one embodiment, the updating the historical route data according to the target recording time of the target route includes:
determining candidate routes with recording times later than the target recording times in the historical route data;
deleting the candidate route in the history route data to update the history route data.
In one embodiment, the selecting the reference route from the historical route data according to the route index identifier includes:
and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as a reference route.
In one embodiment, the performing instance pruning on the historical instance data according to the reference route to obtain target instance data includes:
determining at least one historical route corresponding to the historical instance data;
And according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data.
In one embodiment, the performing instance pruning on the historical instance data according to the reference route and each historical route to obtain target instance data includes:
verifying whether different routes which do not belong to the reference route exist in each historical route;
if so, performing instance deletion on the historical instance corresponding to the difference route in the historical instance data to obtain target instance data.
In a second aspect, the application further provides a page instance management device. The device comprises:
The acquisition module is used for acquiring the historical route data and the historical instance data of the target application;
The selection module is used for selecting a reference route with the recording time earlier than the target recording time from the historical route data according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed;
And the deleting module is used for deleting the historical instance data according to the reference route to obtain target instance data.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:
acquiring historical route data and historical instance data of a target application;
According to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with recording time earlier than the target recording time from the historical route data;
And according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
acquiring historical route data and historical instance data of a target application;
According to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with recording time earlier than the target recording time from the historical route data;
And according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:
acquiring historical route data and historical instance data of a target application;
According to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with recording time earlier than the target recording time from the historical route data;
And according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
According to the page instance management method, the page instance management device, the computer equipment and the storage medium, the reference route is determined according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed; and then, performing instance pruning on the historical instance data according to the reference route to obtain target instance data. According to the above, according to the method and the device, the historical instance data is deleted by referring to the route, so that compared with the operation of caching all page instances in the prior art, the method and the device can effectively reduce the page memory of the target application, and prevent the page memory from exceeding the threshold value, thereby influencing the normal operation of the target application; and the reference route refers to a route with the record time in the historical route data being earlier than the target record time, so when the historical instance data is deleted according to the reference route, the instance with lower use rate recorded in the historical instance data in the reference route determination can be further deleted, and the instance deletion of the historical instance data can be realized on the premise of not influencing the use process of the target application, so that the target instance data is obtained.
Drawings
FIG. 1 is a schematic flow chart of a method for managing page instances according to an embodiment of the present application;
fig. 2 is a schematic flow chart of determining a reference route according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a process for performing example pruning on historical example data according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating another method for managing a page instance according to an embodiment of the present application;
FIG. 5 is a block diagram of a first page instance management apparatus according to an embodiment of the present application;
FIG. 6 is a block diagram illustrating a second page instance management apparatus according to an embodiment of the present application;
FIG. 7 is a block diagram illustrating a third page instance management apparatus according to an embodiment of the present application;
FIG. 8 is a block diagram illustrating a fourth page instance management apparatus according to an embodiment of the present application;
fig. 9 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
In the description of the present application, a description of the terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
In one embodiment, as shown in fig. 1, a method for managing a page instance is provided, where this embodiment is applied to a terminal to illustrate the method, it is understood that the method may also be applied to a server, and may also be applied to a system including the terminal and the server, and implemented through interaction between the terminal and the server. The terminal can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things equipment and portable wearable equipment, and the internet of things equipment can be smart speakers, smart televisions, smart air conditioners, smart vehicle-mounted equipment and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers. In this embodiment, the method includes the steps of:
s101, acquiring historical route data and historical instance data of a target application.
It should be noted that, the history route data records the route of the displayed page triggered by the user in the target application; and each route in the history route data can be arranged in sequence according to the display time of the corresponding page.
For example, when the user triggers the first page in the target application, the first route corresponding to the first page is recorded in the history route data; when the user triggers the second page again, the second route corresponding to the second page is recorded after the first route in the historical route data, and so on, so that the routes are arranged in sequence according to the display time of the corresponding page.
The initialization state of the historical route data is null data;
further, the history instance data records page instances corresponding to the displayed pages triggered by the user in the target application.
In one embodiment of the present application, when the history instance data needs to be acquired, taking a target application as a Vue (framework for constructing a user interface) framework as an example, the Vue framework provides a keep-alive (built-in component of Vue) component, and thus the history instance data may be acquired according to the keep-alive component.
S102, selecting a reference route with recording time earlier than the target recording time from the historical route data according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed.
It should be noted that, in order to ensure that the fluency of the user running the target application is not affected when the historical instance data is subsequently deleted, only the instance of the page with the lower probability of triggering by the user in the historical instance data can be deleted, so as to prevent the user from still needing to regenerate the instance to render the page when triggering the historical page in the target application; in summary, the route with the recording time earlier than the target recording time in the history route data is used as the reference route, and the reference route is the page route with higher triggering probability of the user, so that the reference route with the recording time earlier than the target recording time is selected from the history route data to ensure the smooth proceeding of the subsequent procedure.
In one embodiment of the present application, when it is required to select a reference route having a recording time earlier than a target recording time from the historical route data, the following may be included: determining a route index identifier from historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route; and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as reference routes.
Further illustratively, the rendering operation of the page to be presented may be performed in accordance with the reference route being determined, specifically: acquiring a current virtual node of a page to be displayed, verifying whether a target route is stored in historical instance data, if so, determining a cache virtual node corresponding to the target route from the historical instance data, and associating the cache virtual node with the current virtual node; if not, storing the target route and the current virtual node into the historical instance data. And further, executing rendering operation of the page to be displayed according to the current virtual node.
In one embodiment of the application, at least one candidate virtual node is stored in the history instance data; each candidate virtual node corresponds to a route identifier, when the cache virtual node corresponding to the target route is required to be determined from the historical instance data, whether the route identifier of each candidate virtual node is identical to the target route or not can be verified, and if so, the candidate virtual node with the route identifier identical to the target route is taken as the cache virtual node.
S103, according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
In one embodiment of the application, when the historical instance data needs to be subjected to instance pruning, at least one historical instance corresponding to the reference route can be determined; the historical instance is the instance of the page with higher triggering probability of the user, so that the instance which does not belong to the historical instance in the historical instance data is deleted, and the deleted target instance data is obtained.
In another embodiment of the present application, when instance deletion is required for the historical instance data, at least one historical route corresponding to the historical instance data may also be determined; determining a difference route which does not belong to the reference route and exists in each history route, and deleting the history instance corresponding to the difference route in the history instance data to obtain target instance data.
According to the page instance management method, the reference route is determined according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed; and then, performing instance pruning on the historical instance data according to the reference route to obtain target instance data. According to the above, according to the method and the device, the historical instance data is deleted by referring to the route, so that compared with the operation of caching all page instances in the prior art, the method and the device can effectively reduce the page memory of the target application, and prevent the page memory from exceeding the threshold value, thereby influencing the normal operation of the target application; and the reference route refers to a route with the record time in the historical route data being earlier than the target record time, so when the historical instance data is deleted according to the reference route, the instance with lower use rate recorded in the historical instance data in the reference route determination can be further deleted, and the instance deletion of the historical instance data can be realized on the premise of not influencing the use process of the target application, so that the target instance data is obtained.
In one embodiment, in order to prevent data loss caused by the single-page application when performing page switching and ensure page rendering efficiency, all page instances need to be cached, but when all page instances are cached, the situation of overlarge page memory can occur, so that normal operation of the single-page application is affected. In order to solve the above technical problem, as shown in fig. 2, according to a target route of a page to be displayed in a target application and a target display time of the page to be displayed, a reference route with a recording time earlier than the target recording time is selected from historical route data, which specifically includes the following contents:
S201, determining a route index identification from historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route.
The target recording time of the target route refers to the recording time of the last route corresponding to the target route.
When the route index identifier needs to be determined, it needs to determine whether the historical route data includes the target route, and further, according to the inclusion condition of the historical route data and the target route, different modes are adopted to determine the route index identifier, and the specific method is as follows:
Verifying whether the historical route data contains a target route; if so, the position of the target route in the history route data is used as a route index mark; if not, the historical route data is updated according to the target record time of the target route; and adding the target route into the updated historical route data, and taking the adding position of the target route in the updated historical route data as a route index identifier.
Further, when the historical route data needs to be updated according to the target recording time of the target route, the following specific contents may be included: determining candidate routes with recording times later than the target recording time in the historical route data; candidate routes in the historical route data are deleted to update the historical route data.
In one embodiment of the present application, if the historical route data includes the historical routes respectively: route a, route b, route c, and route d; if the target route is the route c; therefore, if the historical route data contains the target route, the position of the route c in the historical route data is used as the route index identification.
In one embodiment of the present application, if the historical route data includes the historical routes respectively: route a, route b, route c, and route d; if the target route is a route e; the target recording time of the target route refers to the recording time of the last route corresponding to the target route, and the last route is the route c, so that the target recording time of the target route is the recording time of the route c; taking the route which is later than the record time of the route c as a candidate route, wherein the candidate route comprises the route c and the route d; deleting the candidate route in the history route data, wherein the updated history route data is: route a and route b; and adding the route c to updated historical route data (namely route a, route b and route e), and using the adding position of the route c in the updated historical route data as a route index identification.
In one embodiment of the application, attribute change monitoring for each route can be realized by a route monitoring method; taking vue as an example, the change of the route $route (a special variable in the vue. Js framework, which represents the currently active route information) attribute can be directly monitored by the $watch method, a method of monitoring data model changes.
S202, selecting a reference route from the historical route data according to the route index identification.
In one embodiment of the present application, when it is required to select a reference route from the historical route data, the following may be specifically included: and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as reference routes.
The stack bottom position is used for representing the initial position of the historical routing data, namely the position corresponding to the value of 0.
For example, if the historical route data is route a, route b, route c, and route d; the route c is a route index identifier, so that the routes between the stack bottom position and the route index identifier, namely, the route a, the route b and the route c are used as reference routes.
According to the page instance management method, the route index identification is determined from the historical route data, and the reference route is selected from the historical route data according to the route index representation. The method and the device ensure that the historical instance data can be subjected to instance deletion according to the reference route, and realize instance deletion on the historical instance data on the premise of not influencing the use process of the target application, so as to obtain the target instance data.
In one embodiment, as shown in fig. 3, when the historical instance data needs to be subjected to instance deletion, the following may be specifically included:
s301, determining at least one historical route corresponding to the historical instance data.
In one embodiment of the present application, each history instance corresponds to a history route; and carrying out routing query on each history instance contained in the history instance data to obtain at least one history route corresponding to the history instance data.
S302, according to the reference route and each historical route, the historical instance data are subjected to instance deletion, and target instance data are obtained.
It should be noted that, when the example deletion needs to be performed on the history example data, the following may be specifically included: verifying whether different routes which do not belong to the reference route exist in each historical route; if so, deleting the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
Further, if there is no differential route which does not belong to the reference route in each history route, the history instance data is taken as target instance data without instance pruning.
According to the page instance management method, at least one historical route corresponding to the historical instance data is determined, the historical instance data is subjected to instance deletion according to the reference route and each historical route, the target instance data are obtained, the page memory of the target application is effectively reduced, and the influence on the normal operation of the target application due to the fact that the page memory exceeds the threshold value is prevented.
In one embodiment, as shown in fig. 4, when the historical instance data needs to be subjected to instance deletion, the following may be specifically included:
S401, acquiring historical route data and historical instance data of a target application.
S402, verifying whether the historical route data contains a target route; if so, executing S403; if not, S404 is performed.
S403, the position of the target route in the history route data is used as a route index identification.
S404, determining candidate routes with recording times later than the target recording time in the historical route data.
And S405, deleting the candidate routes in the historical route data to update the historical route data.
S406, adding the target route into the updated historical route data, and using the adding position of the target route in the updated historical route data as a route index identification.
S407, taking the route between the stack bottom position and the route index mark in the history route data and the target route as the reference route.
S408, determining at least one historical route corresponding to the historical instance data.
S409, verifying whether a difference route which does not belong to the reference route exists in each history route.
S410, if so, performing instance deletion on the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
According to the page instance management method, the reference route is determined according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed; and then, performing instance pruning on the historical instance data according to the reference route to obtain target instance data. According to the above, according to the method and the device, the historical instance data is deleted by referring to the route, so that compared with the operation of caching all page instances in the prior art, the method and the device can effectively reduce the page memory of the target application, and prevent the page memory from exceeding the threshold value, thereby influencing the normal operation of the target application; and the reference route refers to a route with the record time in the historical route data being earlier than the target record time, so when the historical instance data is deleted according to the reference route, the instance with lower use rate recorded in the historical instance data in the reference route determination can be further deleted, and the instance deletion of the historical instance data can be realized on the premise of not influencing the use process of the target application, so that the target instance data is obtained.
It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a page instance management device for realizing the above-mentioned page instance management method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of one or more page instance management devices provided below may refer to the limitation of the page instance management method described above, and will not be repeated herein.
In one embodiment, as shown in fig. 5, there is provided a page instance management apparatus, including: acquisition module 10, selection module 20, and pruning module 30, wherein:
the acquiring module 10 is configured to acquire historical route data and historical instance data of the target application.
The selection module 20 is configured to select, from the historical route data, a reference route having a recording time earlier than the target recording time according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed.
And the pruning module 30 is configured to prune the historical instance data according to the reference route to obtain the target instance data.
The page instance management device determines a reference route according to a target route of a page to be displayed in a target application and a target display time of the page to be displayed; and then, performing instance pruning on the historical instance data according to the reference route to obtain target instance data. According to the above, according to the method and the device, the historical instance data is deleted by referring to the route, so that compared with the operation of caching all page instances in the prior art, the method and the device can effectively reduce the page memory of the target application, and prevent the page memory from exceeding the threshold value, thereby influencing the normal operation of the target application; and the reference route refers to a route with the record time in the historical route data being earlier than the target record time, so when the historical instance data is deleted according to the reference route, the instance with lower use rate recorded in the historical instance data in the reference route determination can be further deleted, and the instance deletion of the historical instance data can be realized on the premise of not influencing the use process of the target application, so that the target instance data is obtained.
In one embodiment, as shown in fig. 6, there is provided a page instance management apparatus, in which the selection module 20 includes: a first determining unit 21 and a selecting unit 22, wherein:
the first determining unit 21 is configured to determine a route index identifier from the historical route data according to a target route of the page to be displayed in the target application and a target recording time of the target route.
And a selecting unit 22, configured to select a reference route from the historical route data according to the route index identifier.
The selecting unit is specifically configured to use a route located between the stack bottom position and the route index identifier in the historical route data, and the target route as a reference route.
In one embodiment, as shown in fig. 7, there is provided a page instance management apparatus in which the determination unit 21 includes: a determination subunit 211 and an update subunit 212, wherein:
a determining subunit 211 for determining a candidate route having a recording time later than the target recording time in the history route data.
And an updating subunit 212, configured to delete the candidate route in the historical route data, so as to update the historical route data.
In one embodiment, as shown in fig. 8, there is provided a page instance management apparatus in which the pruning module 30 includes: a second determination unit 31 and a pruning unit 32, wherein:
A second determining unit 31, configured to determine at least one history route corresponding to the history instance data.
And a pruning unit 32, configured to prune the historical instance data according to the reference route and each historical route to obtain target instance data.
The deleting unit is specifically used for verifying whether a difference route which does not belong to the reference route exists in each history route; if so, deleting the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
The respective modules in the above-described page instance management apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 9. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a method of page instance management. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by persons skilled in the art that the architecture shown in fig. 9 is merely a block diagram of some of the architecture relevant to the present inventive arrangements and is not limiting as to the computer device to which the present inventive arrangements are applicable, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
acquiring historical route data and historical instance data of a target application;
according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data;
and according to the reference route, performing instance pruning on the historical instance data to obtain target instance data.
In one embodiment, the processor when executing the computer program further performs the steps of: according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data, wherein the method comprises the following steps:
Determining a route index identifier from historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route;
And selecting a reference route from the historical route data according to the route index identification.
In one embodiment, the processor when executing the computer program further performs the steps of: according to the target route of the page to be displayed in the target application and the target record time of the target route, determining the route index identification from the historical route data comprises the following steps:
Verifying whether the historical route data contains a target route;
if so, the position of the target route in the history route data is used as a route index mark;
If not, the historical route data is updated according to the target record time of the target route; and adding the target route into the updated historical route data, and taking the adding position of the target route in the updated historical route data as a route index identifier.
In one embodiment, the processor when executing the computer program further performs the steps of: according to the target record time of the target route, the data updating of the historical route data comprises the following steps:
Determining candidate routes with recording times later than the target recording time in the historical route data;
Candidate routes in the historical route data are deleted to update the historical route data.
In one embodiment, the processor when executing the computer program further performs the steps of: selecting a reference route from the historical route data according to the route index identification, wherein the reference route comprises the following steps:
and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as reference routes.
In one embodiment, the processor when executing the computer program further performs the steps of: according to the reference route, performing instance pruning on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Determining at least one historical route corresponding to the historical instance data;
And according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data.
In one embodiment, the processor when executing the computer program further performs the steps of: according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Verifying whether different routes which do not belong to the reference route exist in each historical route;
If so, deleting the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring historical route data and historical instance data of a target application;
according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data;
and according to the reference route, performing instance pruning on the historical instance data to obtain target instance data.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data, wherein the method comprises the following steps:
Determining a route index identifier from historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route;
And selecting a reference route from the historical route data according to the route index identification.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target route of the page to be displayed in the target application and the target record time of the target route, determining the route index identification from the historical route data comprises the following steps:
Verifying whether the historical route data contains a target route;
if so, the position of the target route in the history route data is used as a route index mark;
If not, the historical route data is updated according to the target record time of the target route; and adding the target route into the updated historical route data, and taking the adding position of the target route in the updated historical route data as a route index identifier.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target record time of the target route, the data updating of the historical route data comprises the following steps:
Determining candidate routes with recording times later than the target recording time in the historical route data;
Candidate routes in the historical route data are deleted to update the historical route data.
In one embodiment, the computer program when executed by the processor further performs the steps of: selecting a reference route from the historical route data according to the route index identification, wherein the reference route comprises the following steps:
and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as reference routes.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the reference route, performing instance pruning on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Determining at least one historical route corresponding to the historical instance data;
And according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Verifying whether different routes which do not belong to the reference route exist in each historical route;
If so, deleting the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:
acquiring historical route data and historical instance data of a target application;
according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data;
and according to the reference route, performing instance pruning on the historical instance data to obtain target instance data.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with the recording time earlier than the target recording time from the historical route data, wherein the method comprises the following steps:
Determining a route index identifier from historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route;
And selecting a reference route from the historical route data according to the route index identification.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target route of the page to be displayed in the target application and the target record time of the target route, determining the route index identification from the historical route data comprises the following steps:
Verifying whether the historical route data contains a target route;
if so, the position of the target route in the history route data is used as a route index mark;
If not, the historical route data is updated according to the target record time of the target route; and adding the target route into the updated historical route data, and taking the adding position of the target route in the updated historical route data as a route index identifier.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the target record time of the target route, the data updating of the historical route data comprises the following steps:
Determining candidate routes with recording times later than the target recording time in the historical route data;
Candidate routes in the historical route data are deleted to update the historical route data.
In one embodiment, the computer program when executed by the processor further performs the steps of: selecting a reference route from the historical route data according to the route index identification, wherein the reference route comprises the following steps:
and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as reference routes.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the reference route, performing instance pruning on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Determining at least one historical route corresponding to the historical instance data;
And according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data.
In one embodiment, the computer program when executed by the processor further performs the steps of: according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data, wherein the method comprises the following steps:
Verifying whether different routes which do not belong to the reference route exist in each historical route;
If so, deleting the historical instance corresponding to the differential route in the historical instance data to obtain target instance data.
The user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric RandomAccess Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (RandomAccess Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static RandomAccess Memory, SRAM) or dynamic random access memory (Dynamic RandomAccess Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.
Claims (11)
1. A method for managing instances of a page, the method comprising:
acquiring historical route data and historical instance data of a target application;
According to the target route of the page to be displayed in the target application and the target display time of the page to be displayed, selecting a reference route with recording time earlier than the target recording time from the historical route data;
And according to the reference route, performing instance deletion on the historical instance data to obtain target instance data.
2. The method according to claim 1, wherein the selecting a reference route with a recording time earlier than the target recording time from the historical route data according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed comprises:
determining a route index identifier from the historical route data according to the target route of the page to be displayed in the target application and the target record time of the target route;
And selecting a reference route from the historical route data according to the route index identification.
3. The method according to claim 2, wherein determining the route index identifier from the historical route data according to the target route of the page to be displayed in the target application and the target recording time of the target route comprises:
verifying whether the historical route data contains the target route;
if so, the position of the target route in the historical route data is used as a route index identification;
if not, carrying out data update on the historical route data according to the target record time of the target route; and adding the target route into the updated historical route data, and using the adding position of the target route in the updated historical route data as a route index identification.
4. A method according to claim 3, wherein said updating the historical route data according to the target recording time of the target route comprises:
determining candidate routes with recording times later than the target recording times in the historical route data;
deleting the candidate route in the history route data to update the history route data.
5. The method of claim 2, wherein selecting a reference route from the historical route data based on the route index identification comprises:
and taking the route between the stack bottom position and the route index identifier in the historical route data and the target route as a reference route.
6. The method according to any one of claims 1-5, wherein performing instance pruning on the historical instance data according to the reference route to obtain target instance data includes:
determining at least one historical route corresponding to the historical instance data;
And according to the reference route and each historical route, carrying out instance deletion on the historical instance data to obtain target instance data.
7. The method of claim 6, wherein performing instance pruning on the historical instance data according to the reference route and each historical route to obtain target instance data comprises:
verifying whether different routes which do not belong to the reference route exist in each historical route;
if so, performing instance deletion on the historical instance corresponding to the difference route in the historical instance data to obtain target instance data.
8. A page instance management apparatus, the apparatus comprising:
The acquisition module is used for acquiring the historical route data and the historical instance data of the target application;
The selection module is used for selecting a reference route with the recording time earlier than the target recording time from the historical route data according to the target route of the page to be displayed in the target application and the target display time of the page to be displayed;
And the deleting module is used for deleting the historical instance data according to the reference route to obtain target instance data.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410187237.9A CN117932186A (en) | 2024-02-20 | 2024-02-20 | Page instance management method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410187237.9A CN117932186A (en) | 2024-02-20 | 2024-02-20 | Page instance management method, device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117932186A true CN117932186A (en) | 2024-04-26 |
Family
ID=90753753
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410187237.9A Pending CN117932186A (en) | 2024-02-20 | 2024-02-20 | Page instance management method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117932186A (en) |
-
2024
- 2024-02-20 CN CN202410187237.9A patent/CN117932186A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111177143B (en) | Key value data storage method and device, storage medium and electronic equipment | |
| CN116910405A (en) | Page processing method, device, computer equipment and storage medium | |
| CN116991800A (en) | File acquisition system, method, device, computer equipment and storage medium | |
| CN117112941A (en) | Dictionary acquisition method, dictionary acquisition device, computer device, storage medium, and program product | |
| CN114924911B (en) | Method, device, equipment and storage medium for backing up effective data of Windows operating system | |
| CN117932186A (en) | Page instance management method, device, computer equipment and storage medium | |
| CN115878625A (en) | Data processing method and device and electronic equipment | |
| CN115168668A (en) | Information recommendation method and device, computer equipment and storage medium | |
| CN113918651A (en) | Business data and capital flow processing method, device, equipment and medium | |
| CN113626650A (en) | Service processing method and device and electronic equipment | |
| CN116541145A (en) | Data calling method, device, computer equipment and computer storage medium | |
| CN114710449B (en) | Flow control method and device for terminal file interaction and computer equipment | |
| CN113900826B (en) | Data processing method, apparatus, computer device, storage medium, and program product | |
| CN114036171B (en) | Application data management method, device, computer equipment and storage medium | |
| CN117076104A (en) | Information base processing method, device, computer equipment and storage medium | |
| CN115269274B (en) | Data recovery method, device, computer equipment and storage medium | |
| CN114647630A (en) | File synchronization method, information generation method, file synchronization device, information generation device, computer equipment and storage medium | |
| CN117648336A (en) | Data query method, device, computer equipment and storage medium | |
| CN117439769A (en) | Page access method, page access device, computer equipment and storage medium | |
| CN117725266A (en) | Load curve data processing method and device and intelligent ammeter | |
| CN117312653A (en) | Service policy determination method, device, computer equipment and storage medium | |
| CN116304407A (en) | Page rendering method, device, computer equipment and storage medium | |
| CN115374114A (en) | Data maintenance method and device, computer equipment and storage medium | |
| CN116910115A (en) | Group query method, device, computer equipment and storage medium | |
| CN114138196A (en) | Power system data storage method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |