CN107479861B - Page processing method and system - Google Patents
Page processing method and system Download PDFInfo
- Publication number
- CN107479861B CN107479861B CN201610399035.6A CN201610399035A CN107479861B CN 107479861 B CN107479861 B CN 107479861B CN 201610399035 A CN201610399035 A CN 201610399035A CN 107479861 B CN107479861 B CN 107479861B
- Authority
- CN
- China
- Prior art keywords
- data
- information
- service data
- page
- description information
- 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.)
- Active
Links
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
- 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/451—Execution arrangements for user interfaces
Abstract
The application discloses a page processing method and a system thereof, wherein the method comprises the following steps: acquiring view template description information and data description information of a plurality of components of a client page; providing a data container and a page container; requesting service data corresponding to the data description information of the component from a corresponding data gateway through the data container; receiving the service data; and loading the components by the page container according to the view template description information, and rendering the loaded components according to the service data. The method and the device meet the requirements of mass business data delivery and personalized data with lower development cost.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a page processing method and system.
Background
Generally speaking, under the condition that the display area of a screen of a mobile client is limited, a personalized algorithm is adopted, calculation is carried out according to multiple dimensions such as the access habits, personal information and geographic positions of a user, different data are returned to the user for display, and therefore a page display mode with thousands of people and thousands of faces is achieved.
Although the number and types of services related to the client page are numerous, the page design usually provides services in several ways, such as: pictures, pictures + text, etc. In the prior art, rich options can be provided for users only by means of rich templates.
The disadvantage of the prior art is that a heavy personalized delivery system and a client page module need to be maintained, the external service and the client code on which the server depends are very complicated, and how to meet the requirements of different page display styles and different business data requirements on the page code of the client is a technical problem which needs to be solved by client development.
Disclosure of Invention
The present application mainly aims to provide a page processing method and a system thereof, so as to overcome the above problems in the prior art.
According to an embodiment of the present application, a page processing method is provided, which includes: acquiring view template description information and data description information of a plurality of components of a client page; providing a data container and a page container; requesting service data corresponding to the data description information of the component from a corresponding data gateway through the data container; receiving the service data; and loading the components by the page container according to the view template description information, and rendering the loaded components according to the service data.
Wherein the view template description information includes: displaying position information and displaying style information; the data description information includes: and displaying the acquired address information of the data and displaying the format information of the data.
Wherein, the step of requesting the service data corresponding to the data description information of the component from the corresponding data gateway through the data container includes: and sending the acquired address information of the display data and the format information of the display data to a corresponding data gateway through the data container, and requesting the service data from a server by the data gateway according to the acquired address information of the display data and the format information of the display data.
The data description information of a plurality of components is packaged into batch data request information and sent to corresponding data gateways, wherein the data description information of each component carries identification information of the corresponding component; and receiving the service data sent by the server through the data gateway, and returning the service data to the corresponding component for rendering processing according to the identification information carried in the service data.
Wherein, still include: and caching the received service data at a terminal where the client is located.
Wherein, still include: acquiring a binding relationship between the data of the component and the view template; and when the service data of the server side is changed, pushing the changed service data to a corresponding component for rendering processing according to the binding relationship between the data and the view template.
Wherein, still include: obtaining list information of components to be displayed of a client page, and rendering the components of the client page according to the list information.
There is also provided, according to an embodiment of the present application, a page processing system, including: the acquisition module is used for acquiring view template description information and data description information of a plurality of components of a client page; the service data request module is used for requesting service data corresponding to the data description information of the component from the corresponding data gateway through the provided data container; a receiving module, configured to receive the service data through the data gateway; and the rendering module is used for loading the components by the provided page container according to the view template description information and rendering the loaded components according to the service data.
Wherein the description information of the view template comprises: displaying position information and displaying style information; the data description information includes: and displaying the acquired address information of the data and displaying the format information of the data.
The service data request module is further configured to send the acquired address information of the display data and the format information of the display data to a corresponding data gateway through the data container, and the data gateway requests the service data from a server according to the acquired address information and the format information of the display data.
The service data request module is further configured to encapsulate data description information of a plurality of components into a batch of data request information, and send the batch of data request information to a corresponding data gateway, where the data description information of each component carries identification information of the corresponding component; the receiving module is further configured to receive the service data sent by the server through the data gateway, and return the service data to the corresponding component for rendering processing according to the identification information carried in the service data.
Wherein, still include: and the cache module is used for caching the received service data at a terminal where the client is located.
The acquisition module is further used for acquiring the binding relationship between the data of the component and the view template; and the rendering module is further used for pushing the changed business data to a corresponding component for rendering operation according to the binding relationship between the data and the view template when the business data of the server is changed.
The acquisition module is further used for acquiring list information of the components to be displayed of the client page; and the rendering module is also used for rendering the components of the client page according to the list information.
According to the embodiment of the application, the page container and the data container are provided, so that the components can be inserted into the container in a plug-in mode, and the page container is responsible for managing rendering, data requirements and the like of the components, so that a large amount of business data release and personalized data requirements are met at low development cost.
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 diagram of a page processing method according to an embodiment of the present application;
FIG. 2 is a flow diagram of a method of page rendering according to an embodiment of the present application;
FIG. 3 is a flow chart of a method of requesting business data according to an embodiment of the application;
FIG. 4 is a block diagram of a system according to one embodiment of the present application;
fig. 5 is a block diagram of a system according to another embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the 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.
Fig. 1 is a flowchart of a page processing method according to an embodiment of the present application, and as shown in fig. 1, the method includes:
step S102, obtaining the view template description information and the data description information of a plurality of components of the client page.
In the embodiment of the application, the client can acquire the view template description information and the data description information of the to-be-displayed component of the client page through the data delivery system. Specifically, the client sends a personalized data request to the data delivery system, and the data delivery system returns personalized data matched with the personalized data request and list information of the components to the client, where the personalized data and the list information of the components may include information such as a display position, a display style, displayed data, and a data format of each component.
Specifically, the view template (template) description information: describing the display type (display style) of the component, for example, the display type of the component can be pictures, words, buttons, or the combination of the above types;
data (data) description information: the business data and data format that the component needs to expose are described. Furthermore, the data description information also comprises data gateway information which is depended by the service data required to be displayed by the acquisition component;
in one embodiment of the present application, a binding relationship between data and a view of a component may also be obtained. The binding relationship between the data and the view describes the association relationship between the view template of the component and the view template presentation data. When the data is changed, the local accurate updating of the page view can be realized according to the binding relationship between the data and the view.
Step S104, providing a data container and a page container.
The data container is responsible for providing data to components in the page container and for link behaviors such as data requests, data caching, data returning and the like. The page container is responsible for uniformly managing components of the page, managing a rendering mechanism, a user interface mechanism and the like.
Step S106, the business data corresponding to the data description information of the component is requested to the corresponding data gateway through the data container.
Specifically, the data description information of the component includes data gateway information on which the required service data is acquired, and the data container directly requests the corresponding data gateway for the required service data.
Step S108, receiving the service data through the data gateway;
and step S110, loading the components by the page container according to the view template description information, and rendering the loaded components according to the service data.
And the page container renders the assembly according to the view template description information of the assembly and the returned service data.
According to the embodiment of the application, the component describes the requirements for the template and the data in a uniform and normative mode, does not need to care about the condition of the page, and is responsible for uniform rendering processing by the page container. In addition, the page container is also responsible for page lifecycle management for creating pages and closing pages.
According to the embodiment of the application, the page container and the data container are provided, so that the components can be inserted into the container in a plug-in mode, and the page container is responsible for managing rendering, data requirements and the like of the components, so that a large amount of business data release and personalized data requirements are met at low development cost.
The page rendering method according to the embodiment of the present application is described in detail below with reference to fig. 2, and as shown in fig. 2, the page rendering method includes the following steps:
step S202, by sending a personalized data request to the data delivery system, detailed description information of the components to be displayed on the client page can be obtained.
The data delivery system, which may also be referred to as a personalized data delivery system, has the capability of delivering personalized business data and providing the personalized business data to the client. Since the present application does not relate to the design of the specific architecture of the data delivery system, it is not described herein again.
Wherein the personalized data request may include: the network condition, the model, the position, the operating system version information, the home page identification, the associated service, the user access habit, the personal attribute information and the like of the terminal where the client is located.
Step S204, the data delivery system returns the personalized data matched with the personalized data request and the list information of the components to the client, where the personalized data and the list information of the components may include information such as a display position, a display style, displayed data, and a data format of each component.
And the data delivered by the data delivery system is determined by calculating according to the multidimensional personalized data contained in the personalized data request.
Step S206, after the client page receives the description information of the component, the page rendering is initiated.
And S208, responding to the rendering initiated by the page, calling an interface of the data container by the page container, and requesting the data required by the data container in batches. Specifically, according to the acquired address information of the display data and the format information of the display data in the data description information, the corresponding service data is requested from the corresponding data gateway through the data container.
Step S210, the data container returns the service data, and the data container may return data in a unified return mode or in a batch mode for multiple times.
Step S212, the page container loads the components according to the description information of the view template, and renders the loaded components according to the service data. Specifically, the page container is implemented as a specific view according to the template description part of the component, and the service data acquired through the data container is sent to the component for rendering processing, so that the component becomes a view which can be directly shown to a user.
A method for requesting service data from a data gateway through a data container according to an embodiment of the present application is described below with reference to fig. 3, where as shown in fig. 3, the method includes:
step 302, obtaining description information of all components in the client page, wherein the description information of the components includes: data description information and view template description information.
Step 304, packaging the data description information of each component into a sub data request, and packaging all the sub data requests into a batch data request, wherein the sub data request of each component carries the identification information of the corresponding component.
Since the request is in a batch form, in order to correspond the return of the batch request to each initiator component, each sub data request needs to carry identification information of the component, and the sub data request is distinguished by a component ID.
And 308, the server maintains data information required by the view template of the component, calls the service data corresponding to each subdata request in sequence and encapsulates the service data and returns the service data to the data gateway, and the data gateway returns the service data to the data container.
Step 310, the data container waits for all requests to be executed, and uniformly encapsulates the returned service data.
In this step, the corresponding service data may also be directly returned to the client after each sub-data request is executed, which is not limited in this application.
And step 312, returning the service data to the corresponding component according to the component ID for rendering processing, and ending the process.
It should be noted that the data of each component supports caching, a uniform cache management mechanism is adopted in the data container to meet the cache requirement of each component, the cache reading and writing process is transparent to the upper component, the component only needs to declare the cache validity duration, and the next request (if the cache validity duration is still in the valid period) can be directly used, so that the situation that the data is requested each time is avoided, and if the declaration is 0, the data cannot be cached.
In an embodiment of the present application, the data displayed by the component is not uniform, and when the server data changes, the client may be notified to refresh in an active notification manner. Specifically, the component container initiates a subscription message request to the server for the component with the attribute of dynamic component. The server establishes and maintains a binding relationship between the data of the components and the view template, when a message pushed by the server arrives (such as a push message, a message of a long link channel, and the like), the server can accurately push the changed business data to the corresponding components by inquiring the binding relationship, and the page container automatically refreshes (renders) the page local view.
Before describing a page processing system according to an embodiment of the present application, a relationship between a client, a server, and a data delivery system is introduced with reference to fig. 4. As shown in fig. 4, the client 41 sends a personalized data request to the data delivery system 42, so as to obtain description information of a component to be displayed on a client page, where the description information at least includes: view template description information and data description information. The component to be presented on the client page may be a data delivery result calculated by the data delivery system 42 through personalization, and the content of the component seen by different users may be different.
The page container 411 and the data container 412 are disposed at the client 41. The data container 412 requests service data corresponding to the data description information of the component from the server 43 through a data gateway (not shown). The page container 411 initiates page rendering, and performs rendering processing on the component according to the view template description information and the service data. That is, the data container 412 is responsible for providing data to components in the page container and for data requests, data caching, data return, and other link behaviors. The page container 411 is responsible for uniformly managing components of the page, managing rendering mechanisms and user interface mechanisms, and the like.
Referring to fig. 5, a block diagram of a page processing system 50 according to an embodiment of the present application includes:
the obtaining module 51 is configured to obtain view template description information and data description information of a plurality of components of the client page.
And a service data request module 52, configured to request service data corresponding to the data description information of the component from a corresponding data gateway through the provided data container.
A receiving module 53, configured to receive the service data.
And the rendering module 54 is configured to load a component according to the view template description information by the provided page container, and perform rendering processing on the loaded component according to the service data.
Wherein the data description information includes: the method comprises the following steps of displaying the acquisition address information of data and the format information of the data, wherein the view template description information comprises: and displaying position information and displaying style information.
In one embodiment, the service data request module 52 is further configured to send, through the data container, the obtained address information of the display data and the format information of the display data to a corresponding data gateway, and the data gateway requests the service data from a server according to the obtained address information and the format information of the display data.
In an embodiment, the service data request module 52 is further configured to encapsulate data description information of multiple components into a batch data request information, and send the batch data request information to a corresponding data gateway, where the data description information of each component carries identification information of the corresponding component. The receiving module 53 is further configured to receive the service data sent by the server through the data gateway, and return the service data to a corresponding component for rendering processing according to the identification information carried in the service data.
In one embodiment, the system 50 further comprises: a buffering module 55, configured to buffer the service data received by the receiving module 53.
In one embodiment, the obtaining module 51 is further configured to obtain a binding relationship between the data of the component and the view template; the rendering module 54 is further configured to, when the service data of the server is changed, push the changed service data to the corresponding component for rendering operation according to the binding relationship between the data and the view template.
In one embodiment, the obtaining module 51 is further configured to obtain list information of components to be displayed on the client page; the rendering module 54 renders the components of the client page according to the list information.
The operation steps of the method correspond to the structural features of the system, and can be referred to one another, which is not described in detail.
In summary, according to the embodiment of the present application, by providing the page container and the data container, the component can be inserted into the container in a plug-in manner, the data container is responsible for requesting the service data to be displayed by the component, and the page container is responsible for managing rendering of the component, so that a large amount of service data delivery and personalized data requirements are met with a low development cost. For a data delivery system, on the front-end page display, it is not necessary to care which data the page uses for rendering, and on the back-end system service, it is also not necessary to care which background service interfaces need to be relied on, but business data is dynamically called in a standard data description manner.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (14)
1. A page processing method is applied to a client and comprises the following steps:
acquiring view template description information and data description information of a plurality of components of a client page and a binding relationship between the data of the components and a view template;
providing a data container and a page container;
requesting service data corresponding to the data description information of the component from a corresponding data gateway through the data container;
receiving the service data;
loading components by the page container according to the view template description information, and rendering the loaded components according to the service data;
the method further comprises the following steps:
and when the service data of the server side is changed, pushing the changed service data to a corresponding component for rendering processing according to the binding relationship between the data and the view template.
2. The method of claim 1,
the view template description information includes: displaying position information and displaying style information;
the data description information includes: and displaying the acquired address information of the data and displaying the format information of the data.
3. The method of claim 2, wherein the step of requesting service data corresponding to the data description information of the component from the corresponding data gateway through the data container comprises:
and sending the acquired address information of the display data and the format information of the display data to a corresponding data gateway through the data container, and requesting the service data from a server by the data gateway according to the acquired address information of the display data and the format information of the display data.
4. The method of claim 1, further comprising:
packaging data description information of a plurality of components into batch data request information and sending the batch data request information to a corresponding data gateway, wherein the data description information of each component carries identification information of the corresponding component;
and receiving the service data sent by the server through the data gateway, and returning the service data to the corresponding component for rendering processing according to the identification information carried in the service data.
5. The method of claim 4, further comprising: and caching the received service data at a terminal where the client is located.
6. The method of claim 1 or 2, further comprising:
acquiring a binding relationship between the data of the component and the view template;
and when the service data of the server side is changed, pushing the changed service data to a corresponding component for rendering processing according to the binding relationship between the data and the view template.
7. The method of claim 1, further comprising:
obtaining list information of components to be displayed of a client page, and rendering the components of the client page according to the list information.
8. A page processing system, applied to a client, comprising:
the acquisition module is used for acquiring view template description information and data description information of a plurality of components of a client page and the binding relationship between the data of the components and the view template;
the service data request module is used for requesting service data corresponding to the data description information of the component from the corresponding data gateway through the provided data container;
a receiving module, configured to receive the service data through the data gateway;
the rendering module is used for loading the components by the provided page container according to the view template description information and rendering the loaded components according to the service data;
the system is further configured to:
and when the service data of the server side is changed, pushing the changed service data to a corresponding component for rendering processing according to the binding relationship between the data and the view template.
9. The system of claim 8,
the description information of the view template comprises: displaying position information and displaying style information;
the data description information includes: and displaying the acquired address information of the data and displaying the format information of the data.
10. The system of claim 9,
the service data request module is further configured to send the acquired address information of the display data and the format information of the display data to a corresponding data gateway through the data container, and the data gateway requests the service data from a server according to the acquired address information and the format information of the display data.
11. The system of claim 8,
the service data request module is further configured to encapsulate data description information of a plurality of components into a batch of data request information, and send the batch of data request information to a corresponding data gateway, where the data description information of each component carries identification information of the corresponding component;
the receiving module is further configured to receive the service data sent by the server through the data gateway, and return the service data to the corresponding component for rendering processing according to the identification information carried in the service data.
12. The system of claim 11, further comprising:
and the cache module is used for caching the received service data at a terminal where the client is located.
13. The system of claim 8 or 9,
the acquisition module is also used for acquiring the binding relationship between the data of the component and the view template;
and the rendering module is further used for pushing the changed business data to a corresponding component for rendering operation according to the binding relationship between the data and the view template when the business data of the server is changed.
14. The system of claim 8,
the acquisition module is also used for acquiring the list information of the components to be displayed of the client page;
and the rendering module is also used for rendering the components of the client page according to the list information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610399035.6A CN107479861B (en) | 2016-06-07 | 2016-06-07 | Page processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610399035.6A CN107479861B (en) | 2016-06-07 | 2016-06-07 | Page processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107479861A CN107479861A (en) | 2017-12-15 |
| CN107479861B true CN107479861B (en) | 2021-04-06 |
Family
ID=60594175
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610399035.6A Active CN107479861B (en) | 2016-06-07 | 2016-06-07 | Page processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107479861B (en) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113055702B (en) * | 2018-02-08 | 2023-06-27 | 广州虎牙信息科技有限公司 | Method, system and client for displaying business components |
| CN108614693B (en) * | 2018-03-21 | 2022-06-24 | 创新先进技术有限公司 | Processing method, device and equipment for page component |
| CN108549671B (en) * | 2018-03-28 | 2022-07-08 | 微梦创科网络科技（中国）有限公司 | Method and device for realizing real-time data acquisition and visualization |
| CN108763551B (en) * | 2018-06-01 | 2022-01-28 | 创新先进技术有限公司 | Page rendering method, device, server and computer readable storage medium |
| CN109165049A (en) * | 2018-07-03 | 2019-01-08 | 北京辰森世纪科技股份有限公司 | Module data processing method and processing device |
| CN109040822B (en) * | 2018-07-16 | 2021-06-22 | 北京奇艺世纪科技有限公司 | Player configuration method and device and storage medium |
| CN109597663A (en) * | 2018-09-06 | 2019-04-09 | 北京微播视界科技有限公司 | Page info processing method, device and electronic equipment |
| CN110109665A (en) * | 2018-10-18 | 2019-08-09 | 神思旭辉医疗信息技术有限责任公司 | A kind of front end UI system and method based on container encapsulation |
| CN111367515B (en) * | 2018-12-25 | 2023-04-28 | 阿里巴巴集团控股有限公司 | Page card development method, device, computing equipment and storage medium |
| CN110321177B (en) * | 2019-06-18 | 2022-06-03 | 北京奇艺世纪科技有限公司 | Mobile application localized loading method and device and electronic equipment |
| CN110457043A (en) * | 2019-07-23 | 2019-11-15 | 上海易点时空网络有限公司 | Page processing method and device based on React |
| CN110381332A (en) * | 2019-08-01 | 2019-10-25 | 广州虎牙科技有限公司 | Direct broadcasting room component processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN110912750B (en) * | 2019-11-29 | 2023-03-21 | 上海维谛信息科技有限公司 | WEB-based data acquisition management method and device |
| CN111198739B (en) * | 2019-12-30 | 2023-08-15 | 广州市百果园信息技术有限公司 | Application view rendering method, device, equipment and storage medium |
| CN111814089B (en) * | 2020-06-30 | 2023-02-17 | 广州市百果园信息技术有限公司 | Page rendering method and device, rendering server and storage medium |
| CN113765868B (en) * | 2020-08-17 | 2023-08-08 | 北京沃东天骏信息技术有限公司 | Service processing method and device |
| CN112214704B (en) * | 2020-08-21 | 2023-08-08 | 长沙市到家悠享网络科技有限公司 | Page processing method and device |
| CN112527258A (en) * | 2020-12-16 | 2021-03-19 | 平安国际智慧城市科技股份有限公司 | Page component development method, system, terminal and computer readable storage medium |
| CN113448543B (en) * | 2021-01-20 | 2024-02-02 | 北京新氧科技有限公司 | Page processing method, device, equipment and system |
| CN113553133B (en) * | 2021-07-26 | 2022-11-04 | 上海哔哩哔哩科技有限公司 | Page display method and system |
| CN114416113B (en) * | 2021-12-30 | 2023-05-12 | 中国电信股份有限公司 | Data release system, method and device based on containerization |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101998167A (en) * | 2010-08-16 | 2011-03-30 | 中兴通讯股份有限公司 | Electronic program guide (EPG) display management method and system |
| US20140297627A1 (en) * | 2011-11-18 | 2014-10-02 | Tencent Technology (Shenzhen) Company Limited | Java application server and method for processing web business |
| CN104391725A (en) * | 2014-12-08 | 2015-03-04 | 畅捷通信息技术股份有限公司 | Page display method and page display device |
| CN105354237A (en) * | 2015-10-09 | 2016-02-24 | 上海瀚之友信息技术服务有限公司 | Business data display method |
-
2016
- 2016-06-07 CN CN201610399035.6A patent/CN107479861B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101998167A (en) * | 2010-08-16 | 2011-03-30 | 中兴通讯股份有限公司 | Electronic program guide (EPG) display management method and system |
| US20140297627A1 (en) * | 2011-11-18 | 2014-10-02 | Tencent Technology (Shenzhen) Company Limited | Java application server and method for processing web business |
| CN104391725A (en) * | 2014-12-08 | 2015-03-04 | 畅捷通信息技术股份有限公司 | Page display method and page display device |
| CN105354237A (en) * | 2015-10-09 | 2016-02-24 | 上海瀚之友信息技术服务有限公司 | Business data display method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107479861A (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107479861B (en) | Page processing method and system | |
| CN110941500B (en) | Interface display method and device | |
| EP3467679B1 (en) | Data processing method and device | |
| CN106533926B (en) | Webpage information spreading method and device | |
| CN107273548B (en) | Dynamic page implementation method and device | |
| CN108200196B (en) | Data storage and query method and system based on distributed architecture | |
| WO2016107465A1 (en) | Method, device, and system for implementing card-type desktop | |
| CN110007916B (en) | Interface rendering method and device of business system and server | |
| CN107092634B (en) | Method and device for realizing page preview | |
| US11019008B2 (en) | Method, public account server, and mobile terminal for sending and generating cards | |
| KR20150113106A (en) | Providing access to information across multiple computing devices | |
| CN111767499A (en) | Page configuration method and device | |
| CN110362547A (en) | Coding, parsing, storage method and the device of journal file | |
| US20070288591A1 (en) | Method, system, and program product for caching application data in a browser cache | |
| CN108076439B (en) | Method and device for pushing messages based on wireless access point | |
| CN109255082B (en) | Page label display method and device | |
| CN109213560B (en) | Method and equipment for displaying information page | |
| CN108520448B (en) | Event management method and device | |
| US20180102996A1 (en) | Payload description for computer messaging | |
| CN112579118A (en) | Method, device, system, medium and equipment for updating configuration information of microservice | |
| CN108664191B (en) | System access method and device | |
| CN112491943A (en) | Data request method, device, storage medium and electronic equipment | |
| US9230022B1 (en) | Customizable result sets for application program interfaces | |
| US11443098B1 (en) | Federated recursive user interface element rendering | |
| CN114037503A (en) | Order processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1248008 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |