CN114637948A - Method and device for processing data - Google Patents

Abstract

The present disclosure discloses a method and an apparatus for processing data, the method is applied to a browser, a web form component runs on the browser, the browser has a database, and the database stores data of a first form, the method includes: receiving a data loading request of the web table component, wherein the data loading request is used for requesting to load target line data in the data of the first table; and responding to the data loading request, and storing part of data containing the target row of data in the database into a memory.

Description

Method and device for processing data

Technical Field

The present disclosure relates to the field of data processing, and in particular, to a method and an apparatus for processing data.

Background

In the web application, a server side sends data requested by a user to a browser and stores the data on a memory. For the display of some scenes, the required data volume may be very large, so that the occupation of the memory is very large, and under the condition of insufficient memory, the browser is jammed or loses response, which directly affects the use of the user.

The traditional solution is data paging loading, and only part of data is stored in a memory each time by paging data sent by a server. Although the memory occupation can be effectively reduced, the browser only stores partial data, so that the operations of sorting and/or screening the full data cannot be completed. These functions can only be completed at the server side, which causes the problem of resource occupation at the server side.

Disclosure of Invention

In view of this, the present disclosure provides a method and an apparatus for processing data, which can effectively reduce the memory occupation of a web application in a large data volume scene, and meanwhile, cannot cause the occupation of server-side resources.

In a first aspect, a method for processing data is provided, where the method is applied to a browser, where a web form component runs on the browser, and the browser has a database, where data of a first form is stored in the database, and the method includes: receiving a data loading request of the web table component, wherein the data loading request is used for requesting to load target line data in the data of the first table; and responding to the data loading request, and storing part of data containing the target row of data in the database into a memory.

Optionally, the data of the first table is stored in the database in units of data blocks, and the partial data is a data block in the database that includes the target row of data.

Optionally, the method is performed by an agent module, the agent module is located between the web form component and the memory, and the agent module is in communication connection with the database.

Optionally, the database of the browser is a transactional database built in the browser.

Optionally, the method further comprises: sorting and/or screening data of a first table in the database.

Optionally, the database stores therein full data of the first table, and a data amount of the full data of the first table is greater than a data amount that can be accommodated by the memory.

In a second aspect, an apparatus for processing data is provided, the apparatus being configured to execute a browser having a web form component running thereon, the browser having a database storing therein data of a first form, the apparatus comprising: a receiving module, configured to receive a data loading request of the web form component, where the data loading request is used to request loading of target line data in the data of the first form; and the response module is used for responding to the data loading request and storing part of data containing the target row of data in the database into a memory.

Optionally, the data of the first table is stored in the database in units of data blocks, and the partial data is a data block in the database that includes the target row of data.

Optionally, the apparatus further comprises: the proxy module is positioned between the web table component and the memory and is in communication connection with the database.

Optionally, the database of the browser is a transactional database built in the browser.

Optionally, the apparatus further comprises: and the data processing module is used for sorting and/or screening the data of the first table in the database.

Optionally, the database stores therein full data of the first table, and a data amount of the full data of the first table is greater than a data amount that can be accommodated by the memory.

In a third aspect, there is provided a computer readable storage medium having stored thereon executable code which, when executed, is capable of implementing the method of the first aspect.

In a fourth aspect, there is provided a computer program product comprising executable code which, when executed, is capable of implementing the method of the first aspect.

The technical scheme provided by the embodiment of the disclosure can effectively solve the problem that the web application occupies the memory in a large data volume scene. The full data sent by the server side is stored in the database of the browser, and then partial data is stored in the memory according to the data loading request of the web table component, so that the occupation of the memory is reduced. Meanwhile, compared with the traditional paging loading technology, the technical scheme provided by the embodiment of the disclosure can directly realize operations such as sorting and/or screening of the full data in the database, and effectively saves resources of the server.

Drawings

Fig. 1 is a diagram of an example system framework of a web application according to an embodiment of the present disclosure.

FIG. 2 is a diagram illustrating an example of a process for processing data by the web form component according to an embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating a method for processing data according to an embodiment of the disclosure.

Fig. 4 is a diagram illustrating an example process of processing data by the web form component according to another embodiment of the present disclosure.

Fig. 5 is a schematic structural diagram of an apparatus for processing data according to an embodiment of the disclosure.

Fig. 6 is a schematic structural diagram of an apparatus for processing data according to yet another embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure are clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments.

The web application is an application program which can be directly accessed through a browser, other software does not need to be installed, and the access of a user is facilitated. Web applications typically employ a browser/server communication mode, i.e., B/S mode. The user and the server communicate through a Hyper Text Transfer Protocol (HTTP), the web application uses a hyper text language (HTML) to link information on the network and store the information in the server, and the user can search information from each web server in the network through a browser.

For ease of understanding, a scenario of a web application involved in an embodiment of the present disclosure is first described in conjunction with fig. 1. Fig. 1 is a diagram of an example system framework of a web application according to an embodiment of the present disclosure. As shown in fig. 1, the system of the web application scenario may include a user terminal 110, a browser 120, and a server 130.

The user terminal 110 may be a device capable of linking to the internet, such as a computer, a smart phone, and a smart wearable device.

The browser 120 can perform relevant processing on the request sent by the user terminal 110, including locating to a corresponding web application server to obtain data requested by the user, and the like. The browser 120 may be, for example, an Application (APP) installed on the user terminal 110, such as an Internet Explorer (IE) browser, a google browser, a firefox browser, and the like.

Server 130, also known as a web application server. The server 130 bears an associated application program for responding to the request of the browser 120 and sending the data requested by the browser 120. The server 130 may be, for example, a physical server, a virtual server, or the like.

Referring to fig. 1, a related description is made of an implementation process of the web application.

In step S112, the user terminal 110 transmits an access request to the browser 120. As an example, when a user opens a google browser, a Uniform Resource Locator (URL) address is entered, which is an addressing mode specifically set for identifying resources on a network. The URL address may be sent to browser 120 as an access request.

In step S123, after receiving the request sent by the user terminal 110, the browser 120 analyzes the access request and sends the processed request information to the server 130. As an example, the google browser parses a URL address input by the user, such as domain name resolution, to obtain an IP address of the web application server corresponding to the URL address. Then, the browser 120 transmits the request of the user terminal 110 to the corresponding server 130 for processing.

In step S132, the server 130 responds to the request of the browser 120 and transmits the data requested by the browser 120. The browser 120 may then load the received data onto a memory, such as a user memory.

In step S121, the browser 120 loads the data in the memory and displays the data in a certain form to the user terminal 110. Optionally, the browser 120 includes a rendering engine, and the rendering engine may present the data stored in the memory to the user terminal 110 in the form of a table, text, picture, and the like.

In a web application, as one embodiment, the web application may be implemented by a web form component. Alternatively, the amount of data needed in the scene of the web form component may be large, such as containing millions or tens of millions of rows of data.

In a scenario of a web form component requiring a large amount of data, the amount of data obtained by the browser 120 from the server 130 side may be very large, and the browser 120 needs to load the large amount of data onto the memory completely, so as to respond to the data loading request of the web form component. Obviously, the memory usage in this case would be very large. If the memory of the user is insufficient, the situation that the browser is jammed and/or loses response can be caused, and the use of the user is directly influenced.

As one embodiment, fig. 2 is a diagram illustrating an example of a process for processing data by a web form component according to an embodiment of the present disclosure. As shown in FIG. 2, the process of processing data may be performed by table element 210 and memory 220.

The form component 210, which may be the aforementioned web form component, is a module that presents data to the user terminal in a form of a table, and as an example, the form component 210 loads the form data stored in the memory 220 in a row data manner, for example, loads the form data according to a sequence number of the row data.

And the memory 220 is used for storing the data sent by the server 130 and received by the browser 120. The memory 220 may be, for example, a Synchronous Dynamic Random Access Memory (SDRAM), a double data rate (DDR SDRAM), or the like.

Referring to fig. 1, after the server 130 sends the table data requested by the user terminal 110 to the browser 120, the browser 120 first loads all the table data to the memory 220. Then, the form component 210 sends a data loading request to the memory, and displays the target line data required to be loaded to the user terminal 110. In this process, if the amount of table data is large, the memory 220 will be occupied very much.

For the problem that the web application occupies too much memory in a large data volume scene, a paging loading technology is adopted in a traditional solution. The paging loading is that the server only loads partial data to the memory each time, thereby reducing the occupation of the memory.

Referring to fig. 1 to 2, after receiving a data request of the browser 120, the server 130 first performs a paging process on table data requested by the browser 120. Specifically, the server 130 divides the table data to be sent to the browser 120 into a plurality of pages, where each page includes a portion of the table data, for example, hundreds of lines of data in each page. Alternatively, the number of rows per page of data in the paged load may be set by the browser 120. When the browser 120 needs to access the table data of a certain page, the server 130 sends the data of the requested page to the browser 120 and loads the data onto the memory 220. When the user browses the next page of table data, the browser 120 sends a data request of the next page to the server 130 again, and loads the table data of the next page to the memory 220. In this way, only one page of data needs to be loaded on the memory 220 at a time, thereby solving the problem of occupation of the memory 220 by the table data.

However, in the above paging loading process, only a part of data in the browser, that is, a certain page of data stored in the memory, is always available. When a user needs to perform relevant operations on the requested full amount of data, such as sorting and/or screening the full amount of data, the operations cannot be completed on the browser. Therefore, these functions can only be performed on the server side, which results in resource occupation of the server 130.

In addition, since the paging load is partial data loaded every time, the browser 120 sends an access request for the page to the server 130 every time the user browses the page of data, and the server 130 sends the page of data to the browser 120. Therefore, the access speed is reduced, and at the same time, the access speed is limited by the network.

In order to solve the existing problems, the embodiment of the present disclosure provides a method for processing data, which can greatly reduce the problem of memory occupation of a web application in a large data volume scene, and meanwhile, compared with a conventional paging loading technology, resources of a server side cannot be occupied.

Fig. 3 is a flowchart illustrating a method for processing data according to an embodiment of the disclosure. A method 300 for processing data according to an embodiment of the present disclosure is described in detail below with reference to fig. 3.

As shown in fig. 3, a method 300 for processing data provided by the embodiment of the present disclosure is applied to a browser, where a web form component runs on the browser, the browser has a database, and the database stores data of a first form.

Alternatively, the data of the first form may be, for example, form data requested by the user, containing data that the web form component needs to load. The first table data may be loaded in line data.

As one embodiment, the database of the browser is a transactional database built into the browser.

The transactional database may be, for example, a database extended DB built in a browser, and the extended DB is locally stored, allowing a large amount of data to be stored, and is therefore suitable for storing a large amount of data. In addition, the database index DB also provides a search interface and establishes an index, so that the operations of searching, screening, sorting and the like of the data in the database index DB can be realized.

As another embodiment, the database stores therein full-amount data of a first table having a data amount larger than that which can be accommodated by the memory.

As can be seen from the foregoing, when the data amount of the full data is too large, for example, larger than the space that the memory can accommodate, the browser may be stuck or lose response, which may affect the use of the user. Thus, for an excessively large total amount of data, it cannot be directly stored to the memory. However, if the whole amount of data is stored in the server, the resources of the server will be wasted.

Therefore, in the embodiment of the present disclosure, the full data of the first table is stored in the database of the browser, and then the database stores the data that needs to be loaded by the web table component to the memory. Therefore, the memory occupation is saved, and the access and loading speed is greatly improved compared with the traditional paging loading method that a loading request is sent to the server every time.

As one embodiment, the data of the first table in the database is sorted and/or filtered. Since the full amount of data in the method 300 of processing data is stored in the browser's database, as an example, the browser's database may be a local database. Therefore, the operations such as sorting and/or screening of the data of the first table can be directly completed in the database, and compared with the traditional paging loading technology which relies on the server end to complete the functions such as sorting and/or screening of the whole data, the waste of server end resources is reduced, and the access speed is improved.

As another embodiment, the data of the first table is stored in the database of the browser in units of data blocks. Alternatively, the data of the first table may be stored in the database extended DB in units of data blocks. After receiving the table data sent by the server, the browser firstly cuts all the table data into a plurality of data blocks, and then stores the data blocks in the database index DB in sequence.

Step S310, receiving a data loading request of the web form component, where the data loading request is used to request loading of target line data in the data of the first form.

Specifically, the browser stores the received data of the first table in the database indexed DB. The web form component, to load the target row data in the data of the first form, sends a load request of the target row data to the database indexed DB. The load request of the target line data may be, for example, a request to load a line or some lines of line data in the data of the first table.

Since the line data that can be displayed on the display page is limited, when the data size of the first table is large, the first table cannot be displayed on the display page at one time. As an example, the web form component may send a load request for corresponding line data to load, and after the line data is exposed, send a next load request for line data.

Step S320, in response to the data loading request, storing a part of data in the database, which includes the target row of data, in the memory.

As one embodiment, the partial data of the target line data may be a data block in the database containing the target line data. As previously described, the data of the first table may be stored in the database in units of data blocks, where each data block may contain a plurality of rows of row data.

Specifically, after receiving a load request of target row data sent by the web form component, the browser loads a data block containing the target row data in the database onto the memory. As an example, the web form component may directly load the target line data from the database, or may first store the data block where the target line data is located on the memory, and then load the target line data by accessing the memory.

However, the web form component accesses the database directly, much slower than accessing memory. Therefore, after the data block containing the target row data is stored in the memory, the web form component directly accesses the memory to load the target row data, and the loading speed of the web form component can be improved. Meanwhile, when the web form component needs to access other rows of data in the data block, the data do not need to be read from the database, and the data are directly loaded in the memory, so that the data loading speed of the web form component is further improved.

Optionally, after the web form component finishes loading the data block stored in the memory, the browser may perform a purge operation on the data block stored in the memory, so as to store a next data block. Therefore, only one data block can be stored in the memory each time, and the occupation of the table data on the memory is further reduced.

Fig. 4 is a diagram illustrating an example process of processing data by the web form component according to an embodiment of the present disclosure. The method 300 of processing data described above is further described below in conjunction with FIG. 4. As shown in FIG. 4, the process by which the web form component processes data may be performed by the form component 210, the memory 220, and a database, which may be, for example, an extended DB 410.

Specifically, after receiving the data of the first table sent by the server, the browser performs segmentation on the data of the first table to form a plurality of data blocks. For example, m data blocks (where m is an integer of 1 or more) each containing n rows of data (where n is an integer of 1 or more) are formed. Then, the browser stores the sliced m data blocks in the database extended DB410 in order.

The table component 210 sends a load request for target row data, for example, a load request for row 1 data, to the database index DB 410. The data block where the 1 st row of data is located is found in the database index DB410 as data block 1, and thus, the browser stores the data block 1 in the memory 220. Table element 210 completes the loading of row 1 data by accessing data block 1 on memory 220. In addition, if the table component 210 needs to load data of a certain row or a certain number of rows 2 to n, the data block 1 stored in the memory 220 can be directly accessed to complete the loading.

When the table component 210 completes the loading of the target line data, the table component 210 sends a load request for the next target line data. For example, the web form component needs to load the data of row n + 1. In the same way, the browser stores the data block 2 in which the (n + 1) th row of data is located in the memory 220, and the form component 210 can load the data in the (n + 1) -2 n th rows of the data block 2 by accessing the memory 220. In addition, when the data block 2 is stored in the memory 220, the browser will clear the data block 1 stored in the memory 220, so that it can be ensured that only one data block is always stored in the memory 220.

In summary, the embodiment of the present disclosure divides the data of the first table sent by the server into a plurality of data blocks, and stores the plurality of data blocks in the database of the browser. And then, storing the data block corresponding to the target line data to the memory according to the loading request of the target line data of the web table component, and ensuring that only one data block is stored on the memory, thereby greatly reducing the occupation of the memory. Meanwhile, compared with the method for reading data from the server side in the paging loading technology, the method provided by the embodiment of the disclosure can directly read the table data from the database of the browser and store the table data in the memory, and the access speed of the method is far faster than that of the network request of paging loading, so that the loading speed of the web table component is greatly improved. In addition, because the full data of the first table is stored in the database of the browser, the operations such as sorting and/or screening the data can be directly completed in the database without being realized at a server, and the resource overhead of the server is effectively saved.

As an example, the method 300 of processing data may also be performed by a proxy module, which may be, for example, a proxy object. Alternatively, the proxy object may be created in advance. The agent module may be located between the web form component and the memory, and the agent module is communicatively coupled to the database.

Referring to fig. 4, a proxy object 420 is located between the table element 210 and the memory 220, and the proxy object 420 is communicatively connected to the database extended DB 410.

Alternatively, a proxy object 420 is created, and then the method of intercepting all attribute access in the proxy object 420, such as a load request for target line data of the form component 210, may be intercepted. In this way, the form component 210 directly sends the load request of the target row data to the proxy object 420, the proxy object 420 completes data acquisition, and the form component 420 does not need to go to the database index DB410 to read data, so that the configuration of an upper layer application, namely, a web form component, does not need to be changed relatively, and therefore the experience of a user can be improved.

Specifically, each time table component 210 loads target line data, a load request for the target line data is sent to proxy object 420. After receiving the load request of the target row data, the proxy object 420 may obtain the target row data from the database indexed DB410 according to the row number of the target row data, and then store the data block containing the target row data in the memory 220. Meanwhile, proxy object 420 returns the corresponding target row data in the data block to table component 210.

In summary, in this process, the form component 210 does not need to interact directly with the database index DB410, but rather is communicatively connected through the proxy object 420. The proxy object 420 shields access differences between the underlying structures, further improving the user experience.

Embodiments of the method for processing data provided by the present disclosure are described in detail above with reference to fig. 1 to 4, and related descriptions are provided below with reference to fig. 5 for embodiments of the apparatus provided by the present disclosure. It is to be understood that the description of the method embodiments corresponds to the description of the apparatus embodiments and therefore reference may be made to the preceding method embodiments for parts not described in detail.

Fig. 5 is a schematic structural diagram of an apparatus for processing data according to an embodiment of the present disclosure. The apparatus 500 for processing data described in fig. 5 may execute a browser having a database storing data of a first table, and a web form component running on the browser. The apparatus 500 for processing data may include a receiving module 510 and a response module 520.

A receiving module 510, configured to receive a data loading request of a web form component, where the data loading request is used to request to load target line data in data of a first form;

the response module 520 may be configured to store, in response to the data loading request, a part of data in the database that includes the target row of data into the memory.

Optionally, the data of the first table is stored in the database in units of data blocks, and the partial data is a data block containing the target row of data in the database.

Optionally, the apparatus 500 for processing data further comprises: and the proxy module is positioned between the web table component and the memory and is in communication connection with the database.

Optionally, the database of the browser is a transactional database built in the browser.

Optionally, the apparatus 500 for processing data further comprises: and the data processing module is used for sorting and/or screening the data of the first table in the database.

Optionally, the database stores therein full data of the first table, and a data amount of the full data of the first table is larger than a data amount that the memory can accommodate.

Fig. 6 is a schematic structural diagram of an apparatus for processing data according to another embodiment of the present disclosure. The apparatus 600 shown in fig. 6 may be a server, a user terminal, or a portable device. The apparatus 600 may include a memory 610 and a processor 620. The memory 610 may be used to store executable code. The processor 620 may be configured to execute executable code stored in the memory 610 to implement the steps in the various methods described previously. In some embodiments, the apparatus 600 may further include a network interface 630, and data exchange between the processor 620 and an external device may be implemented through the network interface 630.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware or any other combination. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the disclosure are all or partially produced when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a Digital Video Disc (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present disclosure, and all the changes or substitutions should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims (13)

1. A method of processing data, the method being applied to a browser having a web form component running thereon, the browser having a database in which data of a first form is stored,

the method comprises the following steps:

receiving a data loading request of the web table component, wherein the data loading request is used for requesting to load target line data in the data of the first table;

and responding to the data loading request, and storing part of data containing the target row of data in the database into a memory.

2. The method of claim 1, wherein the data of the first table is stored in the database in units of data blocks, and the partial data is a data block in the database that includes the target row of data.

3. The method of claim 1, performed by an agent module, the agent module located between the web form component and the memory, the agent module communicatively coupled to the database.

4. The method of claim 1, the browser's database being a transactional database built into the browser.

5. The method of claim 1, further comprising:

sorting and/or screening data of a first table in the database.

6. The method of claim 1, wherein the database stores the full amount of data of the first table, and the full amount of data of the first table is larger than the amount of data that can be accommodated by the memory.

7. An apparatus for processing data, the apparatus being configured to execute a browser having a web form component running thereon, the browser having a database having a first form of data stored therein,

the device comprises:

a receiving module, configured to receive a data loading request of the web form component, where the data loading request is used to request loading of target line data in the data of the first form;

and the response module is used for responding to the data loading request and storing part of data containing the target row of data in the database into a memory.

8. The apparatus of claim 7, the data of the first table is stored in the database in units of data blocks, and the partial data is a data block in the database that includes the target row of data.

9. The apparatus of claim 7, further comprising: the proxy module is positioned between the web table component and the memory and is in communication connection with the database.

10. The apparatus of claim 7, the database of the browser is a transactional database built into the browser.

11. The apparatus of claim 7, further comprising:

and the data processing module is used for sorting and/or screening the data of the first table in the database.

12. The apparatus according to claim 7, wherein the database stores therein the full amount of data of the first table, and the full amount of data of the first table is larger than the amount of data that can be accommodated by the memory.

13. A computer readable storage medium having stored thereon executable code which, when executed, is capable of implementing the method of any one of claims 1 to 6.

Images