CN115495316A - Management method and device for historical page maintenance records - Google Patents

Management method and device for historical page maintenance records Download PDF

Info

Publication number
CN115495316A
CN115495316A CN202211234544.5A CN202211234544A CN115495316A CN 115495316 A CN115495316 A CN 115495316A CN 202211234544 A CN202211234544 A CN 202211234544A CN 115495316 A CN115495316 A CN 115495316A
Authority
CN
China
Prior art keywords
historical
value
target
page
current value
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
Application number
CN202211234544.5A
Other languages
Chinese (zh)
Inventor
孟亚阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
CCB Finetech Co Ltd
Original Assignee
China Construction Bank Corp
CCB Finetech Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp, CCB Finetech Co Ltd filed Critical China Construction Bank Corp
Priority to CN202211234544.5A priority Critical patent/CN115495316A/en
Publication of CN115495316A publication Critical patent/CN115495316A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]

Abstract

The invention discloses a management method and a device for historical page maintenance records, and relates to the technical field of financial information services. One embodiment of the method comprises: responding to the monitored query operation aiming at the target page, and judging whether the target page meets a preset condition; under the condition that the target page meets the preset condition, acquiring a historical maintenance record corresponding to the target page, and acquiring a historical value of a target field in the target page from the historical maintenance record; obtaining a current value of a target field in response to monitoring a submission operation for a target page; and comparing the current value with the historical value, and storing the current value into a historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value. According to the implementation mode, the historical maintenance records are stored in the front-end system, and the back-end service systems are not depended on, so that the coupling degree between the front-end system and the back-end system is reduced, the development workload is reduced, and the development cost is saved.

Description

Management method and device for historical page maintenance records
Technical Field
The invention relates to the technical field of financial information service, in particular to a method and a device for managing historical page maintenance records.
Background
For services needing maintenance in an application system, historical maintenance records need to be inquired during maintenance so as to trace other related problems.
In the related art, the history maintenance record of the page is generally stored in the back-end service system, and then the front-end system calls the query function provided by the back-end service system to query to obtain the history maintenance record. However, when a plurality of services depend on a plurality of different backend service systems, the requirements for providing the query function by the different backend service systems are different, the front-end system needs to repeatedly develop the query page, and the backend system also needs to develop the query interface if the backend system does not support the query, so that the development workload is large and the cost is high.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for managing a historical page maintenance record, where the historical page maintenance record is stored in a front-end system, and does not depend on each back-end service system, so that the coupling degree between the front-end system and the back-end system is reduced, the development workload is reduced, and the development cost is saved.
In order to achieve the above object, according to an aspect of the embodiments of the present invention, there is provided a method for managing a page history maintenance record, including:
responding to the monitored query operation aiming at the target page, and judging whether the target page meets a preset condition or not;
under the condition that the target page meets a preset condition, acquiring a historical maintenance record corresponding to the target page, and acquiring a historical value of a target field in the target page from the historical maintenance record;
responding to the monitored submission operation aiming at the target page, and acquiring the current value of the target field;
and comparing the current value with the historical value, and storing the current value into the historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
Optionally, after saving the current value to the historical maintenance record, the method includes: and taking the current value as the historical value of the target field.
Optionally, the preset condition is that a URL address of the target page exists in a registration configuration file.
Optionally, before determining whether the target page meets a preset condition, the method includes:
and registering and configuring a plurality of page URL addresses, and saving the page URL addresses in the registration configuration file.
Optionally, before determining whether the URL address of the target page exists in the registration configuration file, the method further includes:
and registering and configuring html element blocks in the main page and the sub pages thereof corresponding to the page URL address, wherein the html element blocks comprise a plurality of preset fields, and the target fields are one or more of the preset fields.
Optionally, after comparing the current value with the historical value, the method further includes:
and under the condition that the comparison result indicates that the current value is the same as the historical value, not saving the current value.
Optionally, before obtaining the historical value of the target field from the historical maintenance record, the method includes:
determining that a historical value of the target field exists in the historical maintenance record;
and when the history value of the target field does not exist in the history maintenance record, saving the current value into the history maintenance record.
Optionally, the method further comprises:
and after the historical value of the target field in the target page is acquired from the historical maintenance record, starting a timing task to monitor the target page, acquiring the field value of the target field, judging whether the value of the target field is modified according to the historical value and the field value, and storing the field value in the historical maintenance record under the condition that the value of the target field is modified.
Optionally, before obtaining the history value of the target field in the target page from the history maintenance record, the method includes: constructing a behavior analysis function, and declaring a global variable and a local variable;
comparing the current value to the historical value, comprising:
assigning the historical values to the global variables; assigning the current value to the local variable; and comparing the historical value in the global variable with the current value in the local variable by adopting the behavior analysis function to obtain a comparison result.
According to still another aspect of the embodiments of the present invention, there is provided a management apparatus for a page history maintenance record, including:
the judging module is used for responding to the monitored query operation aiming at the target page and judging whether the target page meets the preset condition or not;
the first acquisition module is used for acquiring a historical maintenance record corresponding to the target page under the condition that the target page meets a preset condition, and acquiring a historical value of a target field in the target page from the historical maintenance record;
the second acquisition module is used for responding to the monitoring of the submission operation aiming at the target page and acquiring the current value of the target field;
and the determining module is used for comparing the current value with the historical value and storing the current value into the historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
Optionally, the determining module is further configured to: and after the current value is saved in the history maintenance record, taking the current value as the history value of the target field.
Optionally, the preset condition is that a URL address of the target page exists in the registration configuration file.
Optionally, the determining module is further configured to: and registering and configuring a plurality of page URL addresses before judging whether the target page meets the preset condition, and storing the page URL addresses in the registration configuration file.
Optionally, the determining module is further configured to: and registering and configuring html element blocks in a main page and sub-pages thereof corresponding to the page URL address before judging whether the URL address of the target page exists in the registration configuration file, wherein the html element blocks comprise a plurality of preset fields, and the target fields are one or more of the preset fields.
Optionally, the determining module is further configured to: after the current value is compared with the historical value, the current value is not saved under the condition that the comparison result indicates that the current value is the same as the historical value.
Optionally, the first obtaining module is further configured to: before obtaining the historical value of the target field from the historical maintenance record, determining that the historical value of the target field exists in the historical maintenance record; and when the history value of the target field does not exist in the history maintenance record, saving the current value into the history maintenance record.
Optionally, the apparatus further comprises a monitoring module configured to: and after the historical value of the target field in the target page is acquired from the historical maintenance record, starting a timing task to monitor the target page, acquiring the field value of the target field, judging whether the value of the target field is modified according to the historical value and the field value, and storing the field value in the historical maintenance record under the condition that the value of the target field is modified.
Optionally, the first obtaining module is further configured to: before obtaining the historical value of the target field in the target page from the historical maintenance record, constructing a behavior analysis function and declaring a global variable and a local variable;
the determining module is further configured to: assigning the historical value to the global variable; assigning the current value to the local variable; and comparing the historical value in the global variable with the current value in the local variable by adopting the behavior analysis function to obtain a comparison result.
According to another aspect of an embodiment of the present invention, there is provided an electronic device including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the management method of the page history maintenance record provided by the invention.
According to still another aspect of the embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for managing a page history maintenance record provided by the present invention.
According to still another aspect of an embodiment of the present invention, there is provided a computer program product including a computer program, which when executed by a processor implements the method for managing page history maintenance records provided by the present invention.
One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of monitoring operation behaviors aiming at a target page, judging whether the target page meets preset conditions, comparing a historical value of a target field obtained from a historical maintenance record during query operation with a current value of the target field obtained during submission operation under the condition that the target page meets the preset conditions, obtaining a comparison result, saving the current value under the condition that the current value is inconsistent with the historical value, and saving the current value into the historical maintenance record to update the historical maintenance record. The method is applied to the front end, and the front end stores historical maintenance records, so that the communication cost of the front end and the rear end service systems can be reduced, redundant research and development workload is reduced, research and development manpower is released, the coupling degree between the front end system and the rear end system is reduced, basic data is provided for the front end to realize a monitoring function, and the defects that in the related technology, the front end system needs to repeatedly develop a query and maintenance record page, the front end system lacks an effective monitoring means, the rear end service system needs to manually research and develop a function of querying and maintaining records, the front end and the rear end have high dependence degree and the coupling degree are overcome.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of a main flow of a management method of a page history maintenance record according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a main flow of another management method for page history maintenance records according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a main flow of a management method for page history maintenance records according to another embodiment of the present invention;
fig. 4 is a flowchart illustrating a method for managing a page history maintenance record according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of the main blocks of a management apparatus of a page history maintenance record according to an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, in the technical solution of the present application, the acquisition, storage, use, processing, etc. of data all conform to the relevant regulations of the national laws and regulations, and do not violate the common customs of the public order.
Fig. 1 is a schematic diagram of a main flow of a management method for a page history maintenance record according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step S101: responding to the monitored query operation aiming at the target page, and judging whether the target page meets a preset condition or not;
step S102: under the condition that the target page meets a preset condition, acquiring a historical maintenance record corresponding to the target page, and acquiring a historical value of a target field in the target page from the historical maintenance record;
step S103: responding to the monitored submission operation aiming at the target page, and acquiring the current value of the target field;
step S104: and comparing the current value with the historical value, and storing the current value into a historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
In the embodiment of the invention, the method is applied to a front-end system to realize the monitoring of the page behavior. In the related technology, after the front-end page is displayed, the query operation executed on the page by the user can be received, the corresponding query result is obtained, the query result is displayed on the front-end page, the user can operate the information on the page, such as adding, modifying, deleting and the like, then the user submits the page after the operation, and the front-end system stores the submitted page data to the back-end service system, so that the back-end service system stores the page data. According to the embodiment of the invention, the page data to be stored is stored in the historical maintenance record of the database of the front-end system according to the service requirement, and the historical maintenance record can be inquired without depending on a back-end service system.
In the embodiment of the invention, the historical maintenance record needing to be stored can be a page of maintenance type transaction, such as 'merchant MCC code blacklist maintenance' transaction of retail loan, the business functions of the transaction include new addition, modification, deletion and maintenance water flow query, which all belong to maintenance operation, and the historical maintenance record stores data corresponding to each maintenance operation.
When query operation for a target page is monitored, a registration configuration file is referred to, whether the target page meets a preset condition is judged, wherein the preset condition can be whether a Uniform Resource Locator (URL) address of the target page exists in the registration configuration file, a historical maintenance record of the target page is obtained under the condition that the URL address of the target page exists in the registration configuration file, and then a historical value of a target field in the target page is obtained from the historical maintenance record. Wherein the history value of the target field may be a last stored value of the target field. The historical maintenance record is stored in a database, a cache or an internal memory of the front-end system, and can be simultaneously stored in a database of the back-end service system.
In the embodiment of the present invention, the preset condition may be that a URL address of the target page exists in the registration configuration file, that is, if the URL address of the target page exists in the registration configuration file or the URL address of the target page matches with the URL address in the registration configuration file, indicating that the URL address of the target page is registered, it is determined that the target page meets the preset condition.
In the embodiment of the present invention, the preset condition may also be that a preset identifier exists in the target page, that is, the preset identifier may be added to the page to be maintained in advance, and if the preset identifier exists in the page, the preset condition is met. Or, the preset condition may also be that a page identifier of the target page exists in the registration configuration file.
In the embodiment of the present invention, before determining whether the target page satisfies the preset condition, the method includes: and registering and configuring a plurality of page URL addresses, and storing the page URL addresses in a registration configuration file. Further comprising: and registering and configuring html element blocks in the main page and the sub-pages thereof corresponding to the page URL address, wherein the html element blocks comprise a plurality of preset fields, and the target field is one or more of the preset fields. That is to say, a plurality of page URL addresses are registered and configured in advance, and html element blocks in each page are configured, where an html element block includes a plurality of preset fields, and is stored in a registration configuration file, and by referring to the registration configuration file, it is determined whether a target page meets a preset condition, that is, the registration configuration file includes a URL address of a page to be maintained and a field in the page where a field value needs to be stored. By referring to the registration configuration file when the page is displayed, the page needing to store the historical maintenance record can be effectively monitored.
In the embodiment of the present invention, after comparing the current value with the historical value, the method further includes: in the case where the comparison result indicates that the current value is the same as the history value, the current value is not saved. That is, if the current value is the same as the history value, it indicates that the value of the target field has not been modified, and the history maintenance record does not need to be updated.
In the embodiment of the present invention, as shown in fig. 2, in a case that a target page meets a preset condition, the method includes:
step S201: acquiring a historical maintenance record corresponding to a target page;
step S202: judging whether a historical value of a target field in a target page exists in the historical maintenance record; if yes, go to step S203, otherwise go to step S204;
step S203: acquiring a historical value of a target field from a historical maintenance record;
step S204: the current value is saved to the history maintenance record.
In the embodiment of the invention, under the condition that the target page meets the preset condition, if a URL address which is the same as the URL address of the target page exists in the registration configuration file, a historical maintenance record of the target page is obtained, whether a historical value of a target field exists in the historical maintenance record is judged, if not, the current value is stored in the historical maintenance record, the current value is taken as the historical value next time, and if so, the historical value of the target field is directly obtained from the historical maintenance record to be compared with the current value.
In an embodiment of the present invention, the method further includes: after the historical value of the target field in the target page is obtained from the historical maintenance record, a timing task is started to monitor the target page, the field value of the target field is obtained, whether the value of the target field is modified or not is judged according to the historical value and the field value, and the field value is stored in the historical maintenance record under the condition that the value of the target field is modified.
In the embodiment of the invention, when a target page is displayed, a timing task is started to perform page behavior analysis on the target page at regular time, namely, a field value of a target field in the target page is obtained at regular time, whether the field value is the same as a historical value of the target field or not is judged, namely, whether modification exists or not is judged, if no modification exists, no processing is performed, if modification exists, the field value is stored into a historical maintenance record, the modification time of the field value is stored at the same time, the query time of the timing task can be used as the modification time, and the execution interval of the timing task can be set in a self-defined mode. The target page is monitored through the timing task, and the operation performed in the target page can be timely acquired, so that a follow-up business party can perform business analysis according to the monitoring result of the timing task.
In the embodiment of the present invention, before obtaining the history value of the target field in the target page from the history maintenance record, the method includes: constructing a behavior analysis function, and declaring a global variable and a local variable; as shown in fig. 3, comparing the current value with the historical value includes:
step S301: assigning the historical value to a global variable;
step S302: assigning the current value to a local variable;
step S303: and comparing the historical value in the global variable with the current value in the local variable by adopting a behavior analysis function to obtain a comparison result.
In the embodiment of the present invention, in the behavior analysis function, the global variable is used to cache the history value, and the local variable is used to cache the current value, and the behavior analysis function may be used to determine whether the URL address of the target page exists in the registration configuration file, that is, determine whether the URL address identical to the URL address of the target page exists in the registration configuration file, if not, no processing is performed, and if so, the current value of the target field in the target page is assigned to the local variable. Obtaining the value of the global variable, and if the value of the global variable does not exist, namely the historical value does not exist in the target field, assigning the current value of the local variable to the global variable; if the value of the global variable exists, namely the historical value exists in the target field, comparing the values in the global variable and the local variable, namely judging whether the historical values in all the variables are the same as the current values in the local variable, if so, not performing any processing, and if not, storing the current values into a historical maintenance record.
Fig. 4 is a flowchart illustrating a method for managing a page history maintenance record according to an embodiment of the present invention. A user opens a current page, performs query operation and submission operation, and simultaneously starts a timing task to monitor the current page; calling a page behavior analysis function, and carrying out page behavior analysis on the current page; reading a registration configuration file, wherein the registration configuration file comprises URL addresses of a plurality of pages and a plurality of preset fields in an html element block; judging whether the URL address of the current page is registered, if not, ending the process, and if so, acquiring the current value of the target field and caching the current value into a local variable; judging whether the global variable is empty or not; if yes, assigning current values in the local variables to all the variables; if not, judging whether the current value in the local variable is consistent with the historical values in all the variables, if so, ending the process, and if not, storing the current value into the historical maintenance record so as to apply the historical maintenance record to a scene of user behavior analysis.
The management method of the page history maintenance record of the embodiment of the invention calls the registration configuration file and the behavior analysis function by monitoring the operation behavior aiming at the target page, judges whether the target page meets the preset condition through the registration configuration file, compares the history value of the target field obtained from the history maintenance record at the front end during the query operation with the current value of the target field obtained during the submission operation by adopting the behavior analysis function under the condition that the target page meets the preset condition, obtains the comparison result, saves the current value under the condition that the current value is inconsistent with the history value, and realizes the update of the history maintenance record. And carrying out timing monitoring on the behavior of the target page by using the timing task, and timely acquiring the modification condition of the target field. The method is applied to the front end, and the front end stores historical maintenance records, so that the communication cost of the front end and the back end service system can be reduced, redundant research and development workload is reduced, research and development manpower is released, the coupling degree between the front end system and the back end system is reduced, basic data is provided for the front end to realize a monitoring function, and the defects that in the related technology, the front end system needs to repeatedly develop an inquiry and maintenance record page, the front end system lacks an effective monitoring means, the back end service system needs to manually research, develop an inquiry and maintenance record function, the front end and the back end have high dependence degree and the coupling degree are overcome.
According to still another aspect of the embodiments of the present invention, as shown in fig. 5, there is provided an apparatus 500 for managing a page history maintenance record, including:
the determining module 501, in response to monitoring the query operation for the target page, determines whether the target page meets a preset condition;
a first obtaining module 502, configured to obtain a historical maintenance record corresponding to a target page when the target page meets a preset condition, and obtain a historical value of a target field in the target page from the historical maintenance record;
the second obtaining module 503, in response to monitoring the submission operation for the target page, obtaining the current value of the target field;
the determining module 504 compares the current value with the historical value, and stores the current value into the historical maintenance record when the comparison result indicates that the current value is different from the historical value.
In this embodiment of the present invention, the determining module 504 is further configured to: after the current value is saved in the history maintenance record, the current value is used as the history value of the target field.
In the embodiment of the present invention, the preset condition is that a URL address of the target page exists in the registration configuration file.
In this embodiment of the present invention, the determining module 501 is further configured to: and registering and configuring a plurality of page URL addresses before judging whether the target page meets the preset condition, and storing the page URL addresses in a registration configuration file.
In this embodiment of the present invention, the determining module 501 is further configured to: before judging whether the URL address of the target page exists in the registration configuration file, registering and configuring html element blocks in the main page and the sub-pages thereof corresponding to the URL address of the page, wherein the html element blocks comprise a plurality of preset fields, and the target fields are one or more of the preset fields.
In this embodiment of the present invention, the determining module 504 is further configured to: after the current value is compared with the history value, the current value is not saved in the case that the comparison result indicates that the current value is the same as the history value.
In this embodiment of the present invention, the first obtaining module 502 is further configured to: before acquiring the historical value of the target field from the historical maintenance record, determining that the historical value of the target field exists in the historical maintenance record; and when the history value of the target field does not exist in the history maintenance record, saving the current value into the history maintenance record.
In an embodiment of the present invention, the apparatus further includes a monitoring module, configured to: after the historical value of the target field in the target page is obtained from the historical maintenance record, a timing task is started to monitor the target page, the field value of the target field is obtained, whether the value of the target field is modified or not is judged according to the historical value and the field value, and the field value is stored in the historical maintenance record under the condition that the value of the target field is modified.
In this embodiment of the present invention, the first obtaining module 502 is further configured to: before obtaining the historical value of a target field in a target page from a historical maintenance record, constructing a behavior analysis function and declaring a global variable and a local variable;
a determining module 504, further configured to: assigning the historical value to a global variable; assigning the current value to a local variable; and comparing the historical value in the global variable with the current value in the local variable by adopting a behavior analysis function to obtain a comparison result.
According to another aspect of an embodiment of the present invention, there is provided an electronic apparatus including: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by one or more processors, the one or more processors realize the management method of the page history maintenance record provided by the invention.
According to still another aspect of the embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for managing a page history maintenance record provided by the present invention.
According to still another aspect of an embodiment of the present invention, there is provided a computer program product including a computer program, and when the computer program is executed by a processor, the method for managing a page history maintenance record provided by the present invention is implemented.
Fig. 6 shows an exemplary system architecture 600 of a page history maintenance record management method or a page history maintenance record management apparatus to which an embodiment of the present invention can be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves as a medium for providing communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with a server 605, via a network 604, to receive or send messages or the like. The terminal devices 601, 602, 603 may have various messaging client applications installed thereon, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the management method for the page history maintenance record provided by the embodiment of the present invention is generally executed by the terminal devices 601, 602, and 603, and accordingly, the management apparatus for the page history maintenance record is generally disposed in the terminal devices 601, 602, and 603.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the use range of the embodiment of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present invention, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a determination module, a first acquisition module, a second acquisition module, and a determination module. The names of the modules do not constitute a limitation on the modules themselves in some cases, for example, the determination module may also be described as a "module that determines whether the target page satisfies a preset condition in response to monitoring a query operation for the target page".
As another aspect, the present invention also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: responding to the monitored query operation aiming at the target page, and judging whether the target page meets a preset condition; under the condition that the target page meets a preset condition, acquiring a historical maintenance record corresponding to the target page, and acquiring a historical value of a target field in the target page from the historical maintenance record; obtaining a current value of a target field in response to monitoring a submission operation for a target page; and comparing the current value with the historical value, and storing the current value into a historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
According to the technical scheme of the embodiment of the invention, the management method of the historical page maintenance record comprises the steps of monitoring the operation behavior of a target page, calling a registration configuration file and a behavior analysis function, judging whether the target page meets a preset condition or not through the registration configuration file, comparing a historical value of a target field obtained from the historical maintenance record at the front end during query operation with a current value of the target field obtained during submission operation by adopting the behavior analysis function under the condition that the target page meets the preset condition, obtaining a comparison result, storing the current value under the condition that the current value is inconsistent with the historical value, and updating the historical maintenance record. And utilizing the timing task to perform timing monitoring on the behavior of the target page and timely acquiring the modification condition of the target field. The method is applied to the front end, and the front end stores historical maintenance records, so that the communication cost of the front end and the rear end service systems can be reduced, redundant research and development workload is reduced, research and development manpower is released, the coupling degree between the front end system and the rear end system is reduced, basic data is provided for the front end to realize a monitoring function, and the defects that in the related technology, the front end system needs to repeatedly develop a query and maintenance record page, the front end system lacks an effective monitoring means, the rear end service system needs to manually research and develop a function of querying and maintaining records, the front end and the rear end have high dependence degree and the coupling degree are overcome.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (21)

1. A management method for page history maintenance records is characterized by comprising the following steps:
responding to the monitored query operation aiming at the target page, and judging whether the target page meets a preset condition;
under the condition that the target page meets a preset condition, acquiring a historical maintenance record corresponding to the target page, and acquiring a historical value of a target field in the target page from the historical maintenance record;
obtaining the current value of the target field in response to monitoring the submission operation aiming at the target page;
and comparing the current value with the historical value, and storing the current value into the historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
2. The method of claim 1, wherein saving the current value to the historical maintenance record comprises:
and taking the current value as the historical value of the target field.
3. The method according to claim 1, wherein the preset condition is that a URL address of the target page exists in a registration configuration file.
4. The method according to claim 3, wherein before determining whether the target page satisfies a preset condition, the method comprises:
and registering and configuring a plurality of page URL addresses, and saving the page URL addresses in the registration configuration file.
5. The method according to claim 4, before determining whether the target page satisfies the preset condition, further comprising:
and registering and configuring html element blocks in the main page and the sub pages thereof corresponding to the page URL address, wherein the html element blocks comprise a plurality of preset fields, and the target fields are one or more of the preset fields.
6. The method of claim 1, wherein after comparing the current value to the historical value, further comprising:
and under the condition that the comparison result indicates that the current value is the same as the historical value, not saving the current value.
7. The method of claim 1, wherein prior to obtaining the historical value of the target field from the historical maintenance record, comprising:
determining that a historical value of the target field exists in the historical maintenance record;
and under the condition that the historical value of the target field does not exist in the historical maintenance record, saving the current value into the historical maintenance record.
8. The method of claim 1, further comprising:
and after the historical value of the target field in the target page is acquired from the historical maintenance record, starting a timing task to monitor the target page, acquiring the field value of the target field, judging whether the value of the target field is modified according to the historical value and the field value, and storing the field value in the historical maintenance record under the condition that the value of the target field is modified.
9. The method of claim 1, wherein before obtaining the historical value of the target field in the target page from the history maintenance record, the method comprises: constructing a behavior analysis function, and declaring a global variable and a local variable;
comparing the current value to the historical value, comprising:
assigning the historical values to the global variables; assigning the current value to the local variable; and comparing the historical value in the global variable with the current value in the local variable by adopting the behavior analysis function to obtain a comparison result.
10. A management apparatus for a page history maintenance record, comprising:
the judging module is used for responding to the monitored query operation aiming at the target page and judging whether the target page meets the preset condition or not;
the first acquisition module is used for acquiring a historical maintenance record corresponding to the target page under the condition that the target page meets a preset condition, and acquiring a historical value of a target field in the target page from the historical maintenance record;
the second acquisition module is used for responding to the monitoring of the submission operation aiming at the target page and acquiring the current value of the target field;
and the determining module is used for comparing the current value with the historical value and storing the current value into the historical maintenance record under the condition that the comparison result indicates that the current value is different from the historical value.
11. The apparatus of claim 10, wherein the determining module is further configured to: and after the current value is saved in the history maintenance record, taking the current value as the history value of the target field.
12. The apparatus according to claim 10, wherein the preset condition is that a URL address of the target page exists in a registration configuration file.
13. The apparatus of claim 12, wherein the determining module is further configured to: and registering and configuring a plurality of page URL addresses before judging whether the target page meets the preset condition, and storing the page URL addresses in the registration configuration file.
14. The apparatus of claim 13, wherein the determining module is further configured to: before judging whether the URL address of the target page exists in the registration configuration file, registering and configuring html element blocks in a main page and sub pages thereof corresponding to the URL address of the page, wherein the html element blocks comprise a plurality of preset fields, and the target fields are one or more of the preset fields.
15. The apparatus of claim 10, wherein the determining module is further configured to: after the current value is compared with the historical value, the current value is not saved under the condition that the comparison result indicates that the current value is the same as the historical value.
16. The apparatus of claim 10, wherein the first obtaining module is further configured to: before obtaining the historical value of the target field from the historical maintenance record, determining that the historical value of the target field exists in the historical maintenance record; and when the history value of the target field does not exist in the history maintenance record, saving the current value into the history maintenance record.
17. The apparatus of claim 10, further comprising a monitoring module to: and after the historical value of the target field in the target page is acquired from the historical maintenance record, starting a timing task to monitor the target page, acquiring the field value of the target field, judging whether the value of the target field is modified according to the historical value and the field value, and storing the field value in the historical maintenance record under the condition that the value of the target field is modified.
18. The apparatus of claim 10, wherein the first obtaining module is further configured to: before obtaining the historical value of the target field in the target page from the historical maintenance record, constructing a behavior analysis function and declaring a global variable and a local variable;
the determining module is further configured to: assigning the historical value to the global variable; assigning the current value to the local variable; and comparing the historical value in the global variable with the current value in the local variable by adopting the behavior analysis function to obtain a comparison result.
19. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-9.
20. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-9.
21. A computer program product comprising a computer program, characterized in that the computer program realizes the method according to any of claims 1-9 when executed by a processor.
CN202211234544.5A 2022-10-10 2022-10-10 Management method and device for historical page maintenance records Pending CN115495316A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211234544.5A CN115495316A (en) 2022-10-10 2022-10-10 Management method and device for historical page maintenance records

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211234544.5A CN115495316A (en) 2022-10-10 2022-10-10 Management method and device for historical page maintenance records

Publications (1)

Publication Number Publication Date
CN115495316A true CN115495316A (en) 2022-12-20

Family

ID=84475281

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211234544.5A Pending CN115495316A (en) 2022-10-10 2022-10-10 Management method and device for historical page maintenance records

Country Status (1)

Country Link
CN (1) CN115495316A (en)

Similar Documents

Publication Publication Date Title
CN111460129A (en) Method and device for generating identification, electronic equipment and storage medium
CN112118352B (en) Method and device for processing notification trigger message, electronic equipment and computer readable medium
CN113282589A (en) Data acquisition method and device
CN110928594A (en) Service development method and platform
CN113312553A (en) Method and device for determining user label
CN116737662A (en) Method, device, electronic equipment and storage medium for processing business data
CN115495316A (en) Management method and device for historical page maintenance records
CN109087097B (en) Method and device for updating same identifier of chain code
CN113722193A (en) Method and device for detecting page abnormity
CN113434754A (en) Method and device for determining recommended API (application program interface) service, electronic equipment and storage medium
CN109213815B (en) Method, device, server terminal and readable medium for controlling execution times
CN113704222A (en) Method and device for processing service request
CN113742617A (en) Cache updating method and device
CN113535768A (en) Production monitoring method and device
CN116450622B (en) Method, apparatus, device and computer readable medium for data warehouse entry
CN112699116A (en) Data processing method and system
CN114285743B (en) Method, device, electronic equipment and storage medium for updating configuration information
CN113362097B (en) User determination method and device
CN113766437B (en) Short message sending method and device
CN113157828B (en) Method and device for pushing data
CN116582594A (en) Method, apparatus, electronic device and computer readable medium for accessing service
CN113760346A (en) Information management method and device
CN114661728A (en) Key recording and managing method applied to redis database
CN113821206A (en) Page embedded point information display method and device
CN113297087A (en) Test method and device

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