CN112163178A - Page data display method and device, storage medium and electronic device - Google Patents
Page data display method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN112163178A CN112163178A CN202011030250.1A CN202011030250A CN112163178A CN 112163178 A CN112163178 A CN 112163178A CN 202011030250 A CN202011030250 A CN 202011030250A CN 112163178 A CN112163178 A CN 112163178A
- Authority
- CN
- China
- Prior art keywords
- data
- page
- page instance
- client
- instance data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000009877 rendering Methods 0.000 claims abstract description 21
- 230000015654 memory Effects 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 18
- 238000007726 management method Methods 0.000 claims description 12
- 238000012800 visualization Methods 0.000 claims description 10
- 230000000007 visual effect Effects 0.000 claims description 9
- 230000008859 change Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 4
- 238000013524 data verification Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 6
- 230000005540 biological transmission Effects 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000008878 coupling Effects 0.000 description 5
- 238000010168 coupling process Methods 0.000 description 5
- 238000005859 coupling reaction Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000013079 data visualisation Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Abstract
The application discloses a page data display method and device, a storage medium and an electronic device. Wherein, the method comprises the following steps: caching page instance data at a client; rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data. The method and the device solve the technical problem that the occupation of server resources is too high in the related technology.
Description
Technical Field
The application relates to the field of webpage display, in particular to a method and a device for displaying page data, a storage medium and an electronic device.
Background
With the advent of the big data era and the continuous development of big data technology, various data become more valuable and have profound influence on various industries. The valuable data are finally provided for the user in a form of forming a visualization large screen by various types of charts, so that the user can use the valuable data more intuitively and dimensionally.
Most applications are designed using the B/S client mode. For large data visualization large-screen applications, the client side often presents some webpages with fixed page structures and no (or few) user interaction events, and the server side provides a data interface with a fixed data format. Obviously, the data interface form from the data display of the client to the data interface form of the server has commonality and consistency.
For example, in patent document CN107562825A, a background data operation module analyzes a user-defined data processing expression to obtain an actually required data set and format, then performs data transmission in a websocket long connection manner, and finally generates a data display page in a server template analysis manner.
For example, in patent document CN106528741A, a display page is generated by dragging an existing component, then data binding is performed on the component by means of http timed polling, and finally a data visualization page is constructed by operating a page DOM node.
The above first scheme has the following disadvantages: the data transmission mode is single, the mode of generating the data display page occupies server resources, and the coupling degree of the front end and the rear end is high, so that the later-period function expansion and maintenance are not facilitated; the second solution has the following disadvantages: the data transmission mode is single, the DOM node is frequently operated in the page generation process, so that the page performance is reduced, the phenomenon of slow page loading or blocking is easy to occur, the functional modules are not clearly divided, and the later expansion and maintenance of the functional modules are not facilitated.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a page data display method and device, a storage medium and an electronic device, so as to at least solve the technical problem that server resources are excessively occupied in the related art.
According to an aspect of an embodiment of the present application, there is provided a method for displaying page data, including: caching page instance data at a client; rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
Optionally, before the client caches the page instance data, the method further includes: sending a data request to a server, wherein the data request is used for requesting the page instance data; and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
Optionally, after obtaining the page instance data returned by the server in response to the data request, the method further includes: detecting an operation of setting a page instance parameter; detecting the operation of setting the visual component parameters; an operation to bind a visualization component to data is detected.
Optionally, after obtaining the page instance data returned by the server in response to the data request, the method further includes: and under the condition that the operation needs to be stored, updating the client cache according to the operation, and informing the server of the update of the client.
Optionally, after obtaining the page instance data returned by the server in response to the data request, the method further includes: rendering the page instance data directly in a page view of the client without a save operation.
Optionally, the operation of detecting the setting of the visualization component parameter includes: detecting the operation of a user registration plug-in module; detecting operation of a theme change plug-in module; detecting an operation on the data verification plug-in module; detecting an operation on a user management plug-in module; detecting the operation of the component library; operation of the rights control plug-in module is detected.
Optionally, after the client caches the page instance data, the method further includes: the plug-ins are managed through a plug-in registry.
According to another aspect of the embodiments of the present application, there is also provided a display device of page data, including: the cache unit is used for caching page instance data at the client; and the rendering unit is used for rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program which, when executed, performs the above-described method.
According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the above method through the computer program.
In the embodiment of the application, a scheme for quickly constructing a large-data visual large-screen application is provided, the page performance is greatly improved, the network transmission frequency is reduced, the network resource occupation is reduced, the expansibility of the tool is improved, the customized development requirement of a user on the tool is met, and the technical problem that the occupation of server resources is overhigh in the related technology can be solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a flow chart of an alternative method for displaying page data according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an alternative core system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an alternative core system according to an embodiment of the present application;
FIG. 4 is a flow chart of an alternative method of displaying page data according to an embodiment of the present application;
FIG. 5 is a schematic diagram of an alternative display device for page data according to an embodiment of the present application;
and
fig. 6 is a block diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In order to solve the following technical problems: the server side can occupy server side resources when performing data rendering of the page, and frequent operation on a DOM node of the page after requesting data can reduce page performance, so that the page is jammed or loaded slowly; the coupling degree of the front end and the rear end is high, the functional modules are not clearly divided, and the expansion and the maintenance of the functional modules in the later period are not facilitated. According to an aspect of an embodiment of the present application, a method embodiment of a method for displaying page data is provided. Fig. 1 is a flowchart of a method for displaying optional page data according to an embodiment of the present application, and as shown in fig. 1, the method may include the following steps:
in step S1, the page instance data is cached at the client.
Optionally, before caching the page instance data, the client sends a data request to the server, where the data request is used to request the page instance data; and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
Optionally, after acquiring the page instance data returned by the server in response to the data request, detecting an operation of setting a page instance parameter; detecting the operation of setting the visual component parameters; an operation to bind a visualization component to data is detected.
Optionally, after the page instance data returned by the server in response to the data request is obtained, in a case that a saving operation is needed, the client cache is updated according to the operation, and the server is notified of the update of the client.
Optionally, the operation of detecting the setting of the visualization component parameter includes: detecting the operation of a user registration plug-in module; detecting operation of a theme change plug-in module; detecting an operation on the data verification plug-in module; detecting an operation on a user management plug-in module; detecting the operation of the component library; operation of the rights control plug-in module is detected.
Step S2, rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
Optionally, after obtaining the page instance data returned by the server in response to the data request, the method further includes: rendering the page instance data directly in a page view of the client without a save operation.
Optionally, after the client caches the page instance data, the method further includes: the plug-ins are managed through a plug-in registry.
Through the steps, a scheme for quickly constructing the large-data visual large-screen application is provided, the page performance is greatly improved, the network transmission frequency is reduced, the network resource occupation is reduced, the expansibility of the tool is improved, the customized development requirement of a user on the tool is met, and the technical problem that the server resource occupation is overhigh in the related technology can be solved.
As an alternative example, the following further details the technical solution of the present application with reference to the specific embodiments of fig. 2 to 4.
As shown in fig. 4, the data caching and page rendering process of the core system is as follows:
s41, the client accesses the background to request all page instance data;
s42, caching the requested page instance data by the client;
s43, the client binds the cache data and the page view in two directions;
s44, the client finishes page rendering;
s45, modifying and setting the page instance parameters, the visualization component parameters and the visualization component data by the user;
s46, whether the user saves the modification of the page instance or not, and only the page rendering is carried out on the page instance if the user does not save the modification of the page instance; and if the modification of the stored page instance is carried out, submitting the modified data to client side cache, submitting the modified data to a server and storing the modified data to a database, and finally rendering the page.
The key implementation of the plug-in architecture is mainly divided into the following four parts:
reasonably dividing a core system and a plug-in module: as shown in fig. 2, the core system is a visual editing function module, and the periphery is a pluggable plug-in module. As shown in fig. 3, the core system mainly has the functions shown in fig. 3.
The management mechanism of the plug-in realizes that: management of the plug-ins is accomplished primarily through a plug-in registry mechanism that lets the core system know which plug-ins are currently available, how to load them, and when to load them. The core system provides a plug-in registry containing information for each plug-in module including its name, location, loading opportunity (load on start, or load on demand), etc.
The connection mode of the plug-in: the core system firstly appoints the plug-in and the connection specification of the plug-in, then the plug-in is realized according to the specification, and finally the core system carries out the dynamic loading of the plug-in according to the specification.
Communication mode between plug-ins: although the plugins are completely decoupled during design, in the actual service operation process, a certain service flow needs the cooperation of a plurality of plugins, which requires communication between two plugins; since there is no direct connection between the plug-ins, the communication must pass through the core system, and therefore the core system needs to provide a plug-in communication mechanism, and the plug-ins can implement the communication between the plug-ins by listening to events triggered by the core system.
The plug-in registry provided by the core system can be realized by adopting the following modes: the plug-in registry can be formulated in a local configuration file mode or a code mode, and if the plug-in registry needs to be managed and maintained, the plug-in registry can be persistently stored in a database, so that the management of the plug-in registry is facilitated.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
According to another aspect of the embodiment of the present application, there is also provided a display apparatus of page data for implementing the display method of page data. Fig. 5 is a schematic diagram of an alternative display device for page data according to an embodiment of the present application, and as shown in fig. 5, the device may include:
a cache unit 51, configured to cache page instance data at a client;
and a rendering unit 53, configured to render the page instance data in the page view of the client according to a binding relationship between the page view and the page instance data.
It should be noted that the caching unit 51 in this embodiment may be configured to execute step S1 in this embodiment, and the rendering unit 53 in this embodiment may be configured to execute step S2 in this embodiment.
Through the module, a scheme for quickly constructing the large-data visual large-screen application is provided, the page performance is greatly improved, the network transmission frequency is reduced, the network resource occupation is reduced, the expansibility of the tool is improved, the customized development requirement of a user on the tool is met, and the technical problem that the occupation of server resources is overhigh in the related technology can be solved.
Optionally, the apparatus of the present application may further comprise: the data acquisition unit is used for sending a data request to a server before caching page instance data at a client, wherein the data request is used for requesting the page instance data; and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
Optionally, the apparatus of the present application may further comprise: the management unit is used for detecting the operation of setting the page instance parameters after acquiring the page instance data returned by the server in response to the data request; detecting the operation of setting the visual component parameters; an operation to bind a visualization component to data is detected.
Optionally, the management unit may be further configured to, after acquiring the page instance data returned by the server in response to the data request, update the client cache according to an operation when a saving operation is required, and notify the server of the update of the client.
Optionally, the management unit may be further configured to, after obtaining the page instance data returned by the server in response to the data request, render the page instance data directly in a page view of the client without a save operation.
Optionally, the management unit may be further configured to: detecting the operation of a user registration plug-in module; detecting operation of a theme change plug-in module; detecting an operation on the data verification plug-in module; detecting an operation on a user management plug-in module; detecting the operation of the component library; operation of the rights control plug-in module is detected.
Optionally, the management unit may be further configured to manage the plug-in through the plug-in registry after the client caches the page instance data.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules as a part of the apparatus may run in a corresponding hardware environment, and may be implemented by software, or may be implemented by hardware, where the hardware environment includes a network environment.
According to another aspect of the embodiment of the application, a server or a terminal for implementing the display method of the page data is also provided.
Fig. 6 is a block diagram of a terminal according to an embodiment of the present application, and as shown in fig. 6, the terminal may include: one or more processors 201 (only one shown), memory 203, and transmission means 205, as shown in fig. 6, the terminal may further comprise an input-output device 207.
The memory 203 may be used to store software programs and modules, such as program instructions/modules corresponding to the method and apparatus for displaying page data in the embodiment of the present application, and the processor 201 executes various functional applications and data processing by running the software programs and modules stored in the memory 203, that is, implements the above-mentioned method for displaying page data. The memory 203 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 203 may further include memory located remotely from the processor 201, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 205 is used for receiving or sending data via a network, and can also be used for data transmission between a processor and a memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 205 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 205 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
Wherein the memory 203 is specifically used for storing application programs.
The processor 201 may call the application stored in the memory 203 via the transmission means 205 to perform the following steps:
caching page instance data at a client;
rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
The processor 201 is further configured to perform the following steps:
sending a data request to a server, wherein the data request is used for requesting the page instance data;
and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
By adopting the embodiment of the application, the page instance data is cached at the client; rendering the scheme of the page instance data' in the page view of the client according to the binding relationship between the page view and the page instance data. The scheme for quickly constructing the large-data visual large-screen application is provided, the page performance is greatly improved, the network transmission frequency is reduced, the network resource occupation is reduced, the expansibility of the tool is improved, the customized development requirement of a user on the tool is met, and the technical problem that the server resource is excessively occupied in the related technology can be solved.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
It can be understood by those skilled in the art that the structure shown in fig. 6 is only an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 6 is a diagram illustrating a structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 6, or have a different configuration than shown in FIG. 6.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
Embodiments of the present application also provide a storage medium. Alternatively, in this embodiment, the storage medium may be a program code for executing a display method of page data.
Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
caching page instance data at a client;
rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
Optionally, the storage medium is further arranged to store program code for performing the steps of:
sending a data request to a server, wherein the data request is used for requesting the page instance data;
and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be 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, units or modules, and may be in an electrical 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 application 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 integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A method for displaying page data is characterized by comprising the following steps:
caching page instance data at a client;
rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
2. The method of claim 1, wherein prior to the client caching the page instance data, the method further comprises:
sending a data request to a server, wherein the data request is used for requesting the page instance data;
and under the condition that the server responds to the data request, acquiring the page instance data returned by the server in response to the data request.
3. The method of claim 2, wherein after obtaining the page instance data returned by the server in response to the data request, the method further comprises:
detecting an operation of setting a page instance parameter;
detecting the operation of setting the visual component parameters;
an operation to bind a visualization component to data is detected.
4. The method of claim 3, wherein after obtaining the page instance data returned by the server in response to the data request, the method further comprises:
and under the condition that the operation needs to be stored, updating the client cache according to the operation, and informing the server of the update of the client.
5. The method of claim 3, wherein after obtaining the page instance data returned by the server in response to the data request, the method further comprises:
rendering the page instance data directly in a page view of the client without a save operation.
6. The method of claim 3, wherein detecting the operation of setting the visualization component parameters comprises:
detecting the operation of a user registration plug-in module;
detecting operation of a theme change plug-in module;
detecting an operation on the data verification plug-in module;
detecting an operation on a user management plug-in module;
detecting the operation of the component library;
operation of the rights control plug-in module is detected.
7. The method of claim 1, wherein after the client caches the page instance data, the method further comprises:
the plug-ins are managed through a plug-in registry.
8. A display device of page data, comprising:
the cache unit is used for caching page instance data at the client;
and the rendering unit is used for rendering the page instance data in the page view of the client according to the binding relationship between the page view and the page instance data.
9. A storage medium, characterized in that the storage medium comprises a stored program, wherein the program when executed performs the method of any of the preceding claims 1 to 7.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the method of any of the preceding claims 1 to 7 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011030250.1A CN112163178A (en) | 2020-09-27 | 2020-09-27 | Page data display method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011030250.1A CN112163178A (en) | 2020-09-27 | 2020-09-27 | Page data display method and device, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112163178A true CN112163178A (en) | 2021-01-01 |
Family
ID=73864191
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011030250.1A Pending CN112163178A (en) | 2020-09-27 | 2020-09-27 | Page data display method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112163178A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113900628A (en) * | 2021-12-09 | 2022-01-07 | 中邮消费金融有限公司 | Vue-based multi-page label instance caching method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105574049A (en) * | 2014-10-30 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Page processing method, device and system of mobile applications |
| CN106446049A (en) * | 2016-08-31 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Page data interaction apparatus and method |
| CN107066631A (en) * | 2017-05-26 | 2017-08-18 | 北京三快在线科技有限公司 | Display methods, device and the electronic equipment of the page |
| CN108334517A (en) * | 2017-01-20 | 2018-07-27 | 华为技术有限公司 | A kind of webpage rendering intent and relevant device |
| CN108427597A (en) * | 2018-03-16 | 2018-08-21 | 崔红保 | Accelerate the method and device of page rendering |
-
2020
- 2020-09-27 CN CN202011030250.1A patent/CN112163178A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105574049A (en) * | 2014-10-30 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Page processing method, device and system of mobile applications |
| CN106446049A (en) * | 2016-08-31 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Page data interaction apparatus and method |
| CN108334517A (en) * | 2017-01-20 | 2018-07-27 | 华为技术有限公司 | A kind of webpage rendering intent and relevant device |
| CN107066631A (en) * | 2017-05-26 | 2017-08-18 | 北京三快在线科技有限公司 | Display methods, device and the electronic equipment of the page |
| CN108427597A (en) * | 2018-03-16 | 2018-08-21 | 崔红保 | Accelerate the method and device of page rendering |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113900628A (en) * | 2021-12-09 | 2022-01-07 | 中邮消费金融有限公司 | Vue-based multi-page label instance caching method |
| CN113900628B (en) * | 2021-12-09 | 2022-02-18 | 中邮消费金融有限公司 | Vue-based multi-page label instance caching method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9990214B2 (en) | Dynamic agent delivery | |
| CN108920703B (en) | HTTP cache optimization method and device | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| CN103475744A (en) | Resource downloading method, device and system on basis of Web application | |
| US20170033980A1 (en) | Agent manager for distributed transaction monitoring system | |
| CN111427773A (en) | Web application resource monitoring method, electronic device and computer readable storage medium | |
| CN110688598A (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN109634753B (en) | Data processing method, device, terminal and storage medium for switching browser kernels | |
| CN108280174A (en) | Front end file construction method and server, page access method and terminal | |
| JP2010272090A (en) | Device, program and method for managing processing request destination | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN112163178A (en) | Page data display method and device, storage medium and electronic device | |
| CN106897456B (en) | Activity information publishing method, activity information driving method, related equipment and system | |
| CN111597785A (en) | Processing method and device of prescription template, electronic equipment and storage medium | |
| CN113536168B (en) | Component processing method and device | |
| CN113163255B (en) | Video playing method, device, terminal and storage medium | |
| CN113961298A (en) | Page switching method, device, equipment and medium | |
| CN111177624B (en) | Website front-end and back-end communication method, device, computer equipment and storage medium | |
| CN112688980B (en) | Resource distribution method and device, and computer equipment | |
| CN113918861A (en) | Icon library display method and device | |
| CN113741913A (en) | Picture configuration method, device and system and storage medium | |
| CN107451182B (en) | File caching method based on Appcache | |
| CN111538553A (en) | Dual-core Web desktop application access processing method and device and storage medium | |
| CN111625239B (en) | Method and device for updating virtual page instance state in SPA | |
| CN111444057A (en) | Page performance data acquisition method and device and computing equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210101 |
|
| RJ01 | Rejection of invention patent application after publication |