CN110795651A - Method, device and electronic device for saving front-end data - Google Patents

Abstract

The present disclosure relates to a method, apparatus, electronic device and computer-readable medium for saving front-end data. The method includes: displaying and monitoring a target page in response to a user operation on a user terminal; obtaining front-end data on the target page when a user triggering a first event is detected on the target page; and storing the front-end data in the local memory of the client. The method, device, electronic device, and computer-readable medium for saving front-end data related to the present disclosure can assist users to save web page data without increasing the workload of the server, and prevent users from losing web page data due to operational errors .

Description

Method, device and electronic device for saving front-end data

technical field

The present disclosure relates to the field of computer information processing, and in particular, to a method, an apparatus, an electronic device, and a computer-readable medium for saving front-end data.

Background technique

With the development of network technology, more and more enterprises and companies have put their service business on the Internet, and users can submit service applications and obtain service assistance through the Internet. Most companies require users to register to confirm the identity of users before providing services to users. Generally speaking, users are required to register, submit relevant information of users themselves to the service website for verification, etc. After passing, you can use the related Internet services provided by the company. When a user makes a specific business application, he often needs to provide some basic information of himself, or improve some data, so that the company can provide services according to the user's characteristics and preferences.

For companies that provide financial products and services, for the safety of the company's funds, users are required to enter a large amount of personal information when registering to check the financial risks of users; when users conduct lending business, they will also need to The user submits a detailed and complete application form. For the convenience of users, user registration and application form submission can be done on the web page. However, due to the large amount of information to be entered, users may temporarily leave the page during registration, or the page may be closed due to misoperation. .

In this case, the user has to fill out the form again and submit the information, which is cumbersome and time-consuming. If the server side monitors web pages in real time for data storage, it will bring a lot of pressure to the server side.

Therefore, there is a need for a new method, apparatus, electronic device and computer-readable medium for saving front-end data.

The above information disclosed in this Background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.

SUMMARY OF THE INVENTION

In view of this, the present disclosure provides a method, device, electronic device, and computer-readable medium for saving front-end data, which can assist users to save web page data without increasing the workload of the server, and prevent users from operating Mistakes and loss of web page data.

Other features and advantages of the present disclosure will become apparent from the following detailed description, or be learned in part by practice of the present disclosure.

According to an aspect of the present disclosure, a method for saving front-end data is proposed, the method includes: displaying and monitoring a target page in response to a user operation on a user terminal; and monitoring on the target page when a user triggers a first event , acquiring the front-end data on the target page; and storing the front-end data in the local storage of the client.

Optionally, it also includes: obtaining a display request of a target page from a client; obtaining front-end data in the local memory according to the display request; and when the front-end data satisfies a time policy, comparing the front-end data with all The target page is jointly displayed in the client.

Optionally, the method further includes: deleting the front-end data corresponding to the target page in the local storage of the user terminal when detecting that the user triggers the second event on the target page.

Optionally, displaying and monitoring the target page in response to the user operation on the client terminal includes: responding to the user operation in the application on the client terminal; and displaying and monitoring the target page based on the HTML 5 language.

Optionally, monitoring the user-triggered first event on the target page includes: monitoring a page closing event on the target page; and/or monitoring a page jump event on the target page; and/or the target A page timeout event is detected on the page.

Optionally, acquiring the front-end data on the target page includes: acquiring an element value in an interface module on the target page.

Optionally, acquiring the element value in the interface module on the target page includes: when the element value is a string type, directly acquiring string data corresponding to the element value; and when the element value is an object When the type is selected, the string data corresponding to the element value is obtained through data type conversion.

Optionally, acquiring the string data corresponding to the element value through data type conversion includes: acquiring element values of other interface modules associated with the object type data; calculating the element values of the other interface modules until the object type is acquired. up to the element value of the data; and converting the element value into string data.

Optionally, storing the front-end data in the local storage of the user terminal includes: screening the front-end data, and storing the filtered front-end data in the local storage of the user terminal.

Optionally, screening the front-end data includes: screening the front-end data according to a user template; and/or screening the front-end data according to a page template.

According to an aspect of the present disclosure, an apparatus for saving front-end data is provided, the apparatus includes: a response module, for displaying and monitoring a target page in response to a user operation on a client; a monitoring module for displaying and monitoring a target page in the target When it is detected on the page that the user triggers the first event, the front-end data on the target page is acquired; and a storage module is used for storing the front-end data in the local storage of the user terminal.

Optionally, it also includes: a request module for obtaining a display request of a target page from a client; a data module for obtaining front-end data in the local memory according to the display request; and a display module for When the front-end data meets the time policy, the front-end data and the target page are displayed on the client side together.

Optionally, the method further includes: a deletion module, configured to delete the front-end data corresponding to the target page in the local storage of the user terminal when detecting that the user triggers the second event on the target page.

Optionally, the response module includes: an operation unit for responding to user operations in the application program on the client; and a target unit for displaying and monitoring the target page based on the HTML 5 language.

Optionally, the monitoring module includes: a closing unit for monitoring a page closing event on the target page; and/or a jumping unit for monitoring a page jumping event on the target page; and/or The timeout unit is used to monitor the page timeout event on the target page.

Optionally, the monitoring module is further configured to acquire element values in the interface module on the target page.

Optionally, the monitoring module includes: a direct unit for directly acquiring string data corresponding to the element value when the element value is a string type; and a conversion unit for directly acquiring the string data corresponding to the element value when the element value is a string type; When the object type is used, the string data corresponding to the element value is obtained through data type conversion.

Optionally, the conversion unit includes: an association subunit, used to obtain element values of other interface modules associated with the object type data; a calculation subunit, used to calculate the element values of the other interface modules until obtaining the up to the element value of the object type data; and a conversion subunit for converting the element value into string data.

Optionally, the storage module is further configured to filter the front-end data, and store the filtered front-end data in a local memory of the user terminal.

Optionally, the storage module includes: a user screening unit for screening the front-end data according to a user template; and/or a page screening unit for screening the front-end data according to a page template.

According to an aspect of the present disclosure, an electronic device is provided, the electronic device includes: one or more processors; a storage device for storing one or more programs; when the one or more programs are processed by the one or more processors Execution causes one or more processors to implement a method as above.

According to an aspect of the present disclosure, a computer-readable medium is provided on which a computer program is stored, the program, when executed by a processor, implements the method as above.

According to the method, apparatus, electronic device, and computer-readable medium for saving front-end data of the present disclosure, when it is detected on the target page that a user triggers a first event, the front-end data on the target page is acquired; The method of storing the front-end data in the local memory of the client can assist the user to save the web page data without increasing the workload of the server, and avoid the user from losing the web page data due to operational errors.

It is to be understood that the foregoing general description and the following detailed description are exemplary only and do not limit the present disclosure.

Description of drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the detailed description of example embodiments thereof with reference to the accompanying drawings. The drawings described below are only some embodiments of the present disclosure, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative efforts.

FIG. 1 is a system block diagram of a method and apparatus for saving front-end data according to an exemplary embodiment.

Fig. 2 is a flowchart of a method for saving front-end data according to an exemplary embodiment.

Fig. 3 is a flowchart of a method for saving front-end data according to another exemplary embodiment.

Fig. 4 is a flowchart of a method for saving front-end data according to another exemplary embodiment.

Fig. 5 is a block diagram of an apparatus for saving front-end data according to an exemplary embodiment.

Fig. 6 is a block diagram of an apparatus for saving front-end data according to another exemplary embodiment.

Fig. 7 is a block diagram of an electronic device according to an exemplary embodiment.

Fig. 8 is a block diagram of a computer-readable medium according to an exemplary embodiment.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments, however, can be embodied in various forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus their repeated descriptions will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided in order to give a thorough understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be employed. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

The block diagrams shown in the figures are merely functional entities and do not necessarily necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices entity.

The flowcharts shown in the figures are only exemplary illustrations and do not necessarily include all contents and operations/steps, nor do they have to be performed in the order described. For example, some operations/steps can be decomposed, and some operations/steps can be combined or partially combined, so the actual execution order may be changed according to the actual situation.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Accordingly, a first component discussed below could be referred to as a second component without departing from the teachings of the concepts of the present disclosure. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

Those skilled in the art can understand that the accompanying drawings are only schematic diagrams of exemplary embodiments, and the modules or processes in the accompanying drawings are not necessarily necessary to implement the present disclosure, and therefore cannot be used to limit the protection scope of the present disclosure.

FIG. 1 is a system block diagram of a method and apparatus for saving front-end data according to an exemplary embodiment.

As shown in FIG. 1 , the system architecture 10 may include terminal devices 101 , 102 , and 103 , a network 104 and a server 105 . The network 104 is a medium used to provide a communication link between the terminal devices 101 , 102 , 103 and the server 105 . The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 101 , 102 and 103 , such as financial service applications, shopping applications, web browser applications, instant messaging tools, email clients, social platform software, and the like.

The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 105 may be a server that provides various services, for example, a background management server that provides support for financial service websites browsed by the terminal devices 101 , 102 , and 103 by the user. The background management server can save and process the received user data.

The terminal devices 101, 102, and 103 may, for example, display and monitor the target page in response to user operations on the client; the terminal devices 101, 102, and 103 may, for example, obtain the Front-end data on the target page; the terminal devices 101, 102, 103 may, for example, store the front-end data in the local memory of the client.

The terminal devices 101, 102, and 103 can also obtain, for example, a display request of the target page from the client; the terminal devices 101, 102, and 103 can also obtain front-end data in the local memory, for example, according to the display request; the terminal devices 101, 102 . 103 , for example, when the front-end data satisfies the time policy, the front-end data and the target page may be displayed on the client side together.

The terminal devices 101 , 102 , and 103 may also delete the front-end data corresponding to the target page in the local storage of the user terminal, for example, when detecting that the user triggers the second event on the target page.

After deleting the front-end data corresponding to the target page in the local storage of the client, the front-end data on the target page may also be stored in the server 105 .

It should be noted that the method for saving front-end data provided by the embodiments of the present disclosure may be executed by terminal devices 101 , 102 , and 103 , and correspondingly, the apparatus for saving front-end data may be provided in the terminal devices 101 , 102 , and 103 middle.

Fig. 2 is a flowchart of a method for saving front-end data according to an exemplary embodiment. The method 20 for saving front-end data includes at least steps S202 to S206.

As shown in FIG. 2, in S202, the target page is displayed and monitored in response to the user operation on the client. Including: responding to user operations in the application program on the client side; and displaying and monitoring the target page based on the HTML 5 language.

For example, the user can display a target page by clicking on the screen in the user terminal. It is worth mentioning that the target page can be set according to the operation of the administrator. Generally speaking, not all pages need to be used. The method in the present disclosure operates. Since the purpose of the present disclosure is to prevent the user from misoperation and data loss when the page fills in more data content, based on the purpose of the present invention, there can be more forms through the settings of the administrator. The data page is monitored.

Among them, the target page is established by the HTML5 language, and HTML5 (WEB front end) is composed of HTML (structure), CSS (style), and JavaScript (behavior). Among them, the structure realizes the tags such as title, list, and picture in the webpage. The style deals with the font size, color, picture size, background of a label, etc. of the title text. The behavior can realize the time in the webpage, the countdown effect in the e-commerce website, the detection of whether the user name is repeated when registering the form, the switching effect of the top picture in the website, and so on. More specifically, front-end data in the present disclosure refers to numerical values in a structure.

In S204, when it is detected on the target page that the user triggers the first event, front-end data on the target page is acquired.

Wherein, monitoring on the target page that the user triggers the first event includes: monitoring a page closing event on the target page; and/or monitoring a page jump event on the target page; and/or monitoring on the target page A page timeout event is detected. The first event can be triggered when the user leaves the current page, or when the user does not operate for a long time, or when the page does not respond due to network reasons.

Different first events can be monitored through different function instructions. For example, whether the user leaves the current page can be monitored through the onbeforeunload function, and the onbeforeunload event is triggered when the current page is about to be left (refreshed or closed). This event can be used to pop up a dialog box, prompting the user whether to continue browsing the page or leave the current page. The default prompt information of the dialog box varies according to different browsers. When the function event is detected, the related operations of the front-end data storage are performed.

In one embodiment, the first event can also be set to any event, the first time can be set to a time event, or an operation event, it can be defined that the user performs front-end data storage 1s after the input of an interface module, or For example, it may be defined that the user performs front-end data storage immediately after operating a certain interface module, etc., and the present disclosure is not limited to this.

In one embodiment, acquiring the front-end data on the target page includes: acquiring an element value in an interface module on the target page. It further includes: when the element value is a string type, directly acquiring the string data corresponding to the element value; and when the element value is an object type, acquiring the character corresponding to the element value through data type conversion string data. The detailed content of "obtaining the front-end data on the target page" will be described in detail in the embodiment corresponding to FIG. 4 .

In S206, the front-end data is stored in the local memory of the client. The method includes: screening the front-end data, and storing the screened front-end data in a local storage (local storage) of the user terminal.

localStorage is a method of storing data on the client-side based on HTML5 language: localStorage is a data storage with no time limit. Before HTML5, these storages were all done by cookies. But cookies are not suitable for storing large amounts of data because they are passed by every request to the server, which makes cookies slow and inefficient. In HTML5, data is not passed by every server request, but data is only used when requested. It makes it possible to store large amounts of data without affecting website performance. For different websites, data is stored in different areas on the user terminal, and a website can only access its own data.

In one embodiment, screening the front-end data includes: screening the front-end data according to a user template; and/or screening the front-end data according to a page template. For the target page, all the front-end data or part of the front-end data on it can be kept. When all the front-end data is saved, the values of the front-end data of all interface modules in the page can be read one by one. Further, only the values of some front-end data can be saved according to the settings. For example, the element values in the interface module in the page can be filtered according to the characteristics of the user, and only the relevant front-end data that the user is interested in can be saved; The characteristics of the page filter the element values in the interface module in the page. For example, if the page is defined as "registration page", the element values in the interface module in the page are filtered according to the settings in the registration page template. Only save and register related front-end data.

The front-end data can also be filtered according to the administrator's settings, and then saved, which the present disclosure is not limited to.

In one embodiment, the method further includes: deleting the front-end data corresponding to the target page in the local storage of the user terminal when the user triggers the second event is detected on the target page. Among them, the second event may be the event that the user submits the page or the user saves the current page. After the user submits or saves the current page, the client sends a data request to the remote server, and at the same time transmits all data on the page. Store it in the remote server. In this case, the client does not need to save the relevant data. In order to save the storage space of the client, the saved front-end data can be deleted.

At present, the front-end data storage of application development is for a single data value, not for a large amount of data. When the user fills in the page information, for a large number of filling operations, the user may refresh the page by mistake, or accidentally click on other pages. Or the user does not want to fill it out, and will add it later when he comes in next time. At this time, the information that the user has filled in will be ignored. The purpose of the present invention is to save the data before the user confirms to submit the data to the background.

The present invention can be installed and set at the user end in the form of a plug-in, and the plug-in can monitor all target pages set by users or administrators.

According to the method for saving front-end data of the present disclosure, when it is detected on the target page that a user triggers a first event, the front-end data on the target page is acquired; and the front-end data is stored in a part of the user terminal The method in the memory can assist the user to save the webpage data on the premise of not increasing the workload of the server, so as to avoid the user from losing the webpage data due to operation errors.

It should be clearly understood that this disclosure describes how to make and use specific examples and that the principles of this disclosure are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.

Fig. 3 is a flowchart of a method for saving front-end data according to another exemplary embodiment. The flow shown in FIG. 3 is a supplementary description of the flow shown in FIG. 2 .

As shown in FIG. 3, in S302, a display request of the target page from the client is obtained. For example, the user performs a click operation on the client to send a display request to open the target page. Also, for example, the user sends a display request to jump to the target page through operations on other applications or web pages.

In S304, the front-end data in the local storage is acquired according to the presentation request. With the method in the present disclosure, all page display requests can be monitored in real time through the plug-in method, and whether the page to be displayed is the target page is determined according to the page number in the display request. When the page to be displayed is the target page, the front-end data related to the target page is acquired from the local memory of the client according to the number or page address of the target page.

In S306, when the front-end data meets the time policy, the front-end data and the target page are displayed on the client side together. The storage time of the front-end data corresponding to the target page is determined, then the storage time is compared with the current time, and when the time policy is satisfied, the front-end data and the target page are displayed on the client side together.

In one embodiment, displaying the front-end data and the target page on the client side together includes, according to the coding of the corresponding page element when the front-end data is stored, filling the front-end data into the corresponding page element, and then Display this page.

In one embodiment, the time policy may be set by the administrator, and may also be set by the user. More specifically, the time policy may be that the time interval between the storage time and the current time does not exceed one week, or one month, or other time intervals. .

In one embodiment, when the front-end data is stored, a time stamp may be added to the front-end data, and the time stamp marks the expiration time of the front-end data. After the front-end data becomes invalid, the front-end data may be deleted directly. Or after the front-end data is invalid, no echo is performed. More specifically, the delete function can be implemented through the removeItem function, removeItem(key): delete the value stored locally for the specified key.

Fig. 4 is a flowchart of a method for saving front-end data according to another exemplary embodiment. The process shown in FIG. 4 is a detailed description of S204 “obtain front-end data on the target page when monitoring the user triggering the first event on the target page” in the process shown in FIG. 2 .

As shown in FIG. 4, in S402, the element value in the interface module on the target page is acquired.

In S404, when the element value is a string type, directly obtain the string data corresponding to the element value. By wrapping elements, you can confirm the elements that need to be stored inside. For example, when the element value is a string type, the string data corresponding to the element value can be directly obtained through the getitem function. getItem(key): Get the value stored locally for the specified key.

In S406, when the element value is an object type, acquire element values of other interface modules associated with the object type data. By wrapping elements, you can confirm the elements that need to be stored inside.

In S408, the element values of the other interface modules are calculated until the element values of the object type data are acquired. For the element value in the associated interface module, the values in all the associated modules can be calculated one by one until the element value in the current interface module is calculated.

In S410, the element value is converted into character string data. For example, when the element value is an object type, the string data corresponding to the element value can be directly obtained through the setitem function. setItem(key, value): store the value in the key field

Those skilled in the art can understand that all or part of the steps for implementing the above-described embodiments are implemented as computer programs executed by the CPU. When the computer program is executed by the CPU, the above-mentioned functions defined by the above-mentioned methods provided by the present disclosure are performed. The program can be stored in a computer-readable storage medium, which can be a read-only memory, a magnetic disk, an optical disk, or the like.

In addition, it should be noted that the above-mentioned drawings are only schematic illustrations of the processes included in the methods according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above figures do not indicate or limit the chronological order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, in multiple modules.

The following are the apparatus embodiments of the present disclosure, which can be used to execute the method embodiments of the present disclosure. For details not disclosed in the apparatus embodiments of the present disclosure, please refer to the method embodiments of the present disclosure.

Fig. 5 is a block diagram of an apparatus for saving front-end data according to an exemplary embodiment. As shown in FIG. 5 , the apparatus 50 for saving front-end data includes: a response module 502 , a monitoring module 504 , a storage module 506 , and a deletion module 508 .

The response module 502 is used to display and monitor the target page in response to the user operation on the client; the response module 502 includes: the operation unit is used to respond to the user operation in the application program on the client; and the target unit is used to display and monitor Said target page based on HTML 5 language.

The monitoring module 504 is configured to obtain front-end data on the target page when monitoring the user triggering the first event on the target page; the monitoring module 504 includes: a closing unit for monitoring the target page by dry monitoring. Page close event: and/or a jump unit, used to monitor a page jump event on the target page; and/or a timeout unit, used to monitor a page timeout event on the target page.

The monitoring module 504 is further configured to acquire element values in the interface module on the target page. The monitoring module 504 includes: a direct unit for directly acquiring the string data corresponding to the element value when the element value is a string type; and a conversion unit for directly acquiring the string data corresponding to the element value when the element value is an object type , and obtain the string data corresponding to the element value through data type conversion. The conversion unit includes: an association subunit for acquiring element values of other interface modules associated with the object type data; a calculation subunit for calculating the element values of the other interface modules until the object type data is acquired. element value; and a conversion subunit for converting the element value into string data.

The storage module 506 is used for storing the front-end data in the local memory of the client. The storage module 506 is further configured to filter the front-end data, and store the filtered front-end data in the local memory of the client.

The storage module 506 includes: a user screening unit for screening the front-end data according to a user template; and/or a page screening unit for screening the front-end data according to a page template.

The deletion module 508 is configured to delete the front-end data corresponding to the target page in the local memory of the user terminal when the user triggers the second event is detected on the target page.

Fig. 6 is a block diagram of an apparatus for saving front-end data according to another exemplary embodiment. As shown in FIG. 6 , the apparatus 60 for saving front-end data further includes a request module 602 , a data module 604 , and a presentation module 606 on the basis of the apparatus 50 for saving front-end data.

The request module 602 is used to obtain the display request of the target page from the client;

The data module 604 is configured to obtain front-end data in the local memory according to the presentation request; and

The display module 606 is configured to display the front-end data together with the target page on the client when the front-end data meets the time policy.

According to the apparatus for saving front-end data of the present disclosure, when a user triggering a first event is detected on the target page, the front-end data on the target page is acquired; and the front-end data is stored in a part of the user terminal The method in the memory can assist the user to save the webpage data on the premise of not increasing the workload of the server, so as to avoid the user from losing the webpage data due to operation errors.

Fig. 7 is a block diagram of an electronic device according to an exemplary embodiment.

An electronic device 700 according to this embodiment of the present disclosure is described below with reference to FIG. 7 . The electronic device 700 shown in FIG. 7 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 7, electronic device 700 takes the form of a general-purpose computing device. Components of the electronic device 700 may include, but are not limited to, at least one processing unit 710, at least one storage unit 720, a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710), a display unit 740, and the like.

Wherein, the storage unit stores program codes, and the program codes can be executed by the processing unit 710, so that the processing unit 710 executes the various exemplary methods according to the present disclosure described in the above-mentioned electronic prescription circulation processing method section of this specification. Implementation steps. For example, the processing unit 710 may perform the steps shown in FIG. 2 , FIG. 3 , and FIG. 4 .

The storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and/or a cache storage unit 7202 , and may further include a read-only storage unit (ROM) 7203 .

The storage unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205 including, but not limited to, an operating system, one or more application programs, other program modules, and programs Data, each or some combination of these examples may include an implementation of a network environment.

The bus 730 may be representative of one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any of a variety of bus structures bus.

The electronic device 700 may also communicate with one or more external devices 700' (eg, keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 700, and/or Communicate with any device (eg, router, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. Such communication may take place through input/output (I/O) interface 750 . Also, the electronic device 700 may communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet) through a network adapter 760 . Network adapter 760 may communicate with other modules of electronic device 700 through bus 730 . It should be appreciated that, although not shown, other hardware and/or software modules may be used in conjunction with electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives and data backup storage systems.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, as shown in FIG. 8 , the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, and the software product can be stored in a non-volatile storage medium (which may be a CD-ROM, a U disk, a removable hard disk) etc.) or on a network, including several instructions to cause a computing device (which may be a personal computer, a server, or a network device, etc.) to perform the above-described method according to an embodiment of the present disclosure.

The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

The computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable storage medium can also be any readable medium other than a readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for performing operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages - such as Java, C++, etc., as well as conventional procedural Programming Language - such as the "C" language or similar programming language. The program code may execute entirely on the user computing device, partly on the user device, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the computer-readable medium realizes the following functions: responding to user operations on the client, displaying and monitoring the target page ; obtaining front-end data on the target page when the user triggers the first event is detected on the target page; and storing the front-end data in the local memory of the user terminal.

Those skilled in the art can understand that the above-mentioned modules may be distributed in the apparatus according to the description of the embodiment, and corresponding changes may also be made in one or more apparatuses that are uniquely different from this embodiment. The modules in the foregoing embodiments may be combined into one module, or may be further split into multiple sub-modules.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure may be embodied in the form of software products, and the software products may be stored in a non-volatile storage medium (which may be CD-ROM, U disk, mobile hard disk, etc.) or on a network , including several instructions to cause a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to an embodiment of the present disclosure.

Exemplary embodiments of the present disclosure have been specifically shown and described above. It should be understood that this disclosure is not limited to the details of construction, arrangements, or implementations described herein; on the contrary, this disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims (10)

1. A method for preserving front-end data, comprising:

responding to user operation on a user side, and displaying and monitoring a target page;

when a first event triggered by a user is monitored on the target page, acquiring front-end data on the target page; and

storing the front-end data in a local memory of the user side.

2. The method of claim 1, further comprising:

acquiring a display request of a target page from a user side;

acquiring front-end data in the local memory according to the display request; and

and when the front-end data meets a time strategy, displaying the front-end data and the target page together in the user side.

3. The method of any of claims 1-2, further comprising:

and deleting front-end data corresponding to the target page in a local memory of the user side when a second event triggered by the user is monitored on the target page.

4. The method of any of claims 1-3, wherein presenting and monitoring the target page in response to a user action on the user side comprises:

responding to user operation in an application program on a user side; and

and displaying and monitoring the target page based on the HTML5 language.

5. The method of any of claims 1-4, wherein monitoring a user triggered first event on the destination page comprises:

monitoring a page closing event on the target page; and/or

Monitoring a page jump event on the target page; and/or

And monitoring a page overtime event on the target page.

6. The method of any of claims 1-5, wherein obtaining front-end data on the target page comprises:

and acquiring element values in the interface module on the target page.

7. The method of any of claims 1-6, wherein obtaining element values in an interface module on the target page comprises:

when the element value is of a character string type, directly acquiring character string data corresponding to the element value; and

and when the element value is of the object type, acquiring character string data corresponding to the element value through data type conversion.

8. An apparatus for preserving front-end data, comprising:

the response module is used for responding to user operation on the user side, and displaying and monitoring the target page;

the monitoring module is used for acquiring front-end data on the target page when a first event triggered by a user is monitored on the target page; and

and the storage module is used for storing the front-end data in a local storage of the user side.

9. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

10. 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-7.

Images