WO2017036309A1 - Procédé, dispositif et appareil de restitution de page - Google Patents

Procédé, dispositif et appareil de restitution de page Download PDF

Info

Publication number
WO2017036309A1
WO2017036309A1 PCT/CN2016/095857 CN2016095857W WO2017036309A1 WO 2017036309 A1 WO2017036309 A1 WO 2017036309A1 CN 2016095857 W CN2016095857 W CN 2016095857W WO 2017036309 A1 WO2017036309 A1 WO 2017036309A1
Authority
WO
WIPO (PCT)
Prior art keywords
html
target
module
page
resources
Prior art date
Application number
PCT/CN2016/095857
Other languages
English (en)
Chinese (zh)
Inventor
朱盛家
Original Assignee
阿里巴巴集团控股有限公司
朱盛家
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 朱盛家 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017036309A1 publication Critical patent/WO2017036309A1/fr

Links

Images

Classifications

    • 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

Definitions

  • the present application relates to the field of network communication technologies, and in particular, to a page rendering method, apparatus, and device.
  • Page rendering is the process by which the client browser displays HTML (Hyper Text Markup Language) code in a browser window according to predefined rules.
  • HTML Hyper Text Markup Language
  • the client browser When the client browser renders the HTML page, it needs to obtain various resources for rendering the page from the server, and implement the HTML page rendering by loading the acquired resources.
  • the HTML document framework can be divided into multiple HTML modules according to different functions.
  • the client browser When rendering the HTML page portion corresponding to any HTML module, the client browser sequentially requests each server different HTML module in a serial manner. Type resources, and after requesting each type of resource, load these resources by manually calling JavaScript to complete the rendering of the HTML page part.
  • the application provides a page rendering method, device and device to solve the problem that the overall speed of the existing page rendering is slow.
  • a page rendering method is provided, where the method is applied to a client device, including:
  • a page rendering apparatus the apparatus being applied to a client device, the apparatus comprising:
  • a traversing unit for traversing a file object model DOM node of each HTML module of the HTML page when accessing the HTML page through the browser;
  • a requesting unit configured to, when traversing to a target DOM node of the current target HTML module, request a plurality of target resources of the target HTML module in parallel according to the attribute information defined in the target DOM node;
  • a rendering unit configured to render the target HTML module according to a relationship between the plurality of target resources.
  • a client device including:
  • processor a memory for storing the processor executable instructions
  • processor is configured to:
  • the target of the target HTML module may be requested in parallel according to the attribute information defined in the target DOM node to the server.
  • FIG. 1 is a flow chart of an embodiment of a page rendering method of the present application
  • FIG. 2 is a schematic diagram of a scenario for performing page rendering by applying an embodiment of the present application
  • FIG. 3 is a flow chart of another embodiment of a page rendering method of the present application.
  • FIG. 4 is a hardware structural diagram of a client device where a page rendering device of the present application is located;
  • FIG. 5 is a block diagram of an embodiment of a page rendering apparatus of the present application.
  • FIG. 6 is a block diagram of another embodiment of a page rendering apparatus of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a flowchart of an embodiment of a page rendering method of the present application, which may be Applied to the client device, including the following steps:
  • Step 101 When accessing the HTML page through the browser, traverse the DOM node of each HTML module of the HTML page.
  • the HTML page when the user launches the browser on the client device and accesses the HTML page through the browser, the HTML page may be first divided into multiple HTML modules.
  • the HTML page may be divided into different functions according to different functions. Multiple parent HTML modules. Further, for any parent HTML module, the parent HTML module can also be divided into multiple child HTML modules.
  • the HTML module of the HTML page may be divided according to different functions of the HTML page. For example, the image display area, the video display area, and the text display area on the HTML page may be divided into different HTML modules, and further, It is also possible to divide the text content fixed area and the text content change area in the text display area into different HTML modules.
  • the DOM node of the HTML module can be defined by the WEB native layout, the DOM node is used to mark the area of the corresponding HTML module in the HTML page, and the attribute information can be added on the DOM node, the attribute
  • the information includes the resource path of multiple resources of the HTML module, such as the address or port of the storage resource on the server.
  • each HTML page contains a plurality of HTML modules, at which point the client device begins to traverse the DOM nodes of each HTML module, performing the same operations for each DOM node client device traversed. Therefore, for convenience of description, the currently traversed HTML module is referred to as a target HTML module, and the DOM node of the target HTML module is referred to as a target DOM node.
  • Step 102 When traversing to the target DOM node of the current target HTML module, request multiple target resources of the target HTML module to the server in parallel according to the attribute information defined in the target DOM node.
  • the attribute information of the target DOM node may be read, the resource path of the plurality of target resources of the target HTML module is obtained, and then the resources of each target resource are obtained.
  • the path sends a resource request for obtaining these target resources in parallel to the server by calling JavaScript.
  • Resources can include: HTML Files, CSS (Cascading Style Sheets) files, JS (JavaScript) files, JSON (JavaScript Object Notation, JS Object Markup) data, etc.
  • Step 103 Render the target HTML module according to the relationship between the multiple target resources.
  • a request status may be set for each resource request, and the request status is used to mark whether the corresponding target resource has been acquired.
  • the target resources may be sequentially loaded according to the dependencies between the target resources, the target HTML module is synthesized, and finally the synthesized HTML module is added to the target DOM. In the node, thus completing the rendering of the target HTML module. It can be seen that when the DOM nodes of all the HTML modules are traversed and the rendering of all the HTML modules is completed, the rendering of the entire HTML page can be completed.
  • the loading process when the target resources are sequentially loaded according to the dependency relationship between the target resources is consistent with the prior art.
  • the target resource includes an HTML file, a CSS file, a JS file, and JSON data
  • the HTML file is firstly used according to the HTML file.
  • the HTML document framework is loaded, and then the HEML document framework is modified by the JS file.
  • the HTML document framework is further modified by the CSS file and the JSON data, thereby rendering the HTML page portion corresponding to the target HTML module.
  • FIG. 2 is a schematic diagram of a scenario for implementing page rendering in the application of the embodiment of the present application.
  • FIG. 2 is an example of rendering an HTML page of an OPOA (One Page One Application).
  • FIG. 2 includes a client device side for loading an HTML page, generally referred to as a mobile phone, a tablet, a PC, and the like configured with a browser; and a server side providing various resources for loading an HTML page, the server side You can deploy a distributed server, for example, CDN (Content Delivery Network, Content Distribution Network) server.
  • CDN Content Delivery Network, Content Distribution Network
  • OPOA refers to a WEB page is an application.
  • all HTML documents are transmitted to the WEB browser.
  • the HTML page will be in the current WEB page. load.
  • FIG. 2 assuming that an OPOA includes n HTML pages, the rendering process of each HTML page can be implemented by using the solution provided by the embodiment of the present application. Taking the HTML page 2 shown in FIG.
  • the HTML page 2 is divided into m HTML modules, and the resources of each HTML module are stored on the server side, and the rendering process of each HTML module is consistent to the HTML module 2
  • the client device sends the resource request to the server in parallel, and after obtaining all the resources including the HTML file, the JS file, the CSS file, and the JSON data, the dependence between the resources is utilized.
  • the relationship is rendered out of the corresponding portion of the HTML page 2 corresponding to the HTML module 2.
  • the page rendering process of the present application will be described in detail below through the embodiment shown in FIG. 3 in conjunction with the scenario diagram shown in FIG. 2.
  • FIG. 3 it is a flowchart of another embodiment of a page rendering method of the present application.
  • the embodiment may be applied to a client device, including the following steps:
  • Step 301 When the HTML page is accessed through the browser, the HTML page is divided into a plurality of HTML modules.
  • the HTML page when the user starts the browser on the client device and accesses the HTML page through the browser, the HTML page may be first divided into multiple HTML modules.
  • the HTML page may be divided into different functions according to different functions.
  • the parent HTML module can also be divided into multiple child HTML modules.
  • the HTML page 2 is divided into m HTML modules, which may include a parent HTML module, and/or a sub-HTML module.
  • the HTML page when the HTML module of the HTML page is divided, the HTML page may be divided according to different functions of the HTML page.
  • the image display area, the video display area, and the text display area on the HTML page may be divided into different HTML modules.
  • the text content fixed area and the text content change area in the text display area may be divided into different HTML module; additionally, for the OPOA shown in FIG. 2, different HTML pages may contain partially identical page content, for example, when rendering HTML page 1, divide HTML page 1 into several HTML modules, if HTML page 2 is The divided HTML module is the same as the page content of an HTML module divided in the HTML page 1.
  • the rendering time and rendering resources of 2 are not limited in this embodiment of the present application.
  • Step 302 Define attribute information of the DOM node of each HTML module through the WEB native layout.
  • Native development generally refers to the development of a native development language.
  • the native development language is the programming language used to develop the entire system.
  • DOM is a document model described in an object-oriented manner, and is also a tree representation of the data and structure on the page. In this way, the DOM defines the objects needed to represent and modify the document, the behavior and properties of the object, and the relationships between the objects.
  • the DOM node of the HTML module may be defined by the WEB native layout, and the DOM node is used to mark the corresponding HTML module in the HTML page.
  • An area and may add attribute information on the DOM node, where the attribute information includes resource paths of multiple resources of the HTML module, such as an address or a port of the storage resource on the server; further, the HTML module may be defined on the DOM node. Other information such as name.
  • attribute information can be added to the DOM node defined for the HTML module 2
  • the attribute information includes the HTML file, the JS file, the CSS file, and the JSON of the HTML module 2.
  • the resource path where the data is stored on the server side.
  • Step 303 Traverse the DOM node of each HTML module of the HTML module.
  • each HTML page contains a plurality of HTML modules, at which point the client device begins to traverse the DOM nodes of each HTML module, performing the same operations for each DOM node client device traversed. Therefore, for the convenience of description, the HTML module currently traversed is referred to as the target HTML module, and the DOM section of the target HTML module is referred to. The point is called the target DOM node.
  • Step 304 When traversing to the target DOM node of the current target HTML module, the attribute information of the target DOM node is read, and the resource paths of the plurality of target resources of the target HTML module are obtained.
  • the attribute information of the DOM node defined in step 302 can be read, and the HTML file of the HTML module 2 and the JS are obtained. Resource paths for files, CSS files, and JSON data.
  • Step 305 Send a resource request for acquiring the target resource to the server in parallel by calling JavaScript according to the resource path of each target resource.
  • a high-level scripting language that can be directly interpreted by a browser can be utilized.
  • the advanced scripting language can be JavaScript
  • the JavaScript is an object- and event-driven and relatively secure.
  • Client scripting language can be JavaScript
  • the client device may concurrently send the resource request of the HTML file and the resource of the JS file according to the resource path. Requests, resource requests for CSS files, and resource requests for JSON data.
  • Step 306 Set a request status for each resource request, and the request status is used to mark whether the corresponding target resource has been acquired.
  • a request status may be set for each resource request, and the request status is used to mark whether the corresponding target resource has been obtained, for example, when If a target resource is not obtained, the request status of the target resource is “waiting”. When a target resource has been acquired, the request status of the target resource is “completed”.
  • Step 307 When it is determined that all the target resources are acquired according to the set request status, the target HTML modules are synthesized after sequentially loading the target resources according to the dependency relationship between the target resources.
  • the resource request of the set HTML file when the resource request of the set HTML file, the resource request of the JS file, the resource request of the CSS file, and the resource request of the JSON data The status is "completed", and it can be determined that all resources of the HTML module 2 are obtained.
  • the process of loading the HTML module 2 according to the dependency relationship between the resources is consistent with the prior art, and may include: first loading the HTML document frame of the HTML module 2 according to the HTML file, and then modifying the HEML document frame through the JS file. Finally, the HTML document framework is further modified by the CSS file and the JSON data, thereby rendering the HTML page portion corresponding to the target HTML module.
  • Step 308 Add the target HTML module to the target DOM node to complete rendering of the target HTML module.
  • Step 309 Determine whether the DOM node of all the HTML modules is traversed. If yes, execute step 310; otherwise, return to step 303.
  • Step 310 Determine to complete the rendering of the HTML page and end the current process.
  • the complete HTML page can be loaded on the browser.
  • the present application also provides an embodiment of a page rendering device and a client device.
  • Embodiments of the present page rendering apparatus can be applied to various client devices on which a browser is installed, for example, the client device can include a mobile phone, a tablet, a PC, and the like.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical device, the processor of the client device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • FIG. 4 a hardware structure diagram of the client device where the page rendering device is located, except for the processor, memory, network interface, and non-volatile storage shown in FIG.
  • the client device where the device is located in the embodiment may also include other hardware according to the actual function of the device, which is not shown in FIG. 4 .
  • FIG. 5 it is a block diagram of an embodiment of a page rendering apparatus of the present application:
  • the apparatus includes a traversal unit 510, a request unit 520, and a rendering unit 530.
  • the traversing unit 510 is configured to traverse the file object model DOM node of each HTML module of the HTML page when accessing the HTML page through the browser;
  • the requesting unit 520 is configured to, when traversing to the target DOM node of the current target HTML module, request the plurality of target resources of the target HTML module in parallel according to the attribute information defined in the target DOM node;
  • the rendering unit 530 is configured to render the target HTML module according to the relationship between the multiple target resources.
  • FIG. 6 a block diagram of another embodiment of the page rendering apparatus of the present application is as follows:
  • the apparatus includes a dividing unit 610, a defining unit 620, a traversing unit 630, a requesting unit 640, a rendering unit 650, and a judging unit 660 and a determining unit 670.
  • the dividing unit 610 is configured to divide the HTML page into multiple HTML modules.
  • the defining unit 620 is configured to define attribute information of a DOM node of each HTML module by using a WEB native layout, where the DOM node is used to mark an area of the HTML module in the HTML page, where the attribute information includes multiple HTML modules.
  • the traversing unit 630 is configured to traverse the file object model DOM node of each HTML module of the HTML page when accessing the HTML page through the browser;
  • the requesting unit 640 is configured to, when traversing to the target DOM node of the current target HTML module, request the plurality of target resources of the target HTML module in parallel according to the attribute information defined in the target DOM node;
  • a rendering unit 650 configured to render the target HTML module according to a relationship between the plurality of target resources
  • the determining unit 660 is configured to determine whether the DOM node of all the HTML modules is traversed
  • the determining unit 670 is configured to: if the DOM node of all the HTML modules is traversed, the determination is completed. Rendering of the HTML page.
  • the request unit 640 can include (not shown in FIG. 6):
  • An information reading subunit configured to read attribute information of the target DOM node, and obtain a resource path of multiple target resources of the target HTML module;
  • the request sending subunit is configured to send, according to the resource path of each target resource, a resource request for acquiring the target resource to the server in parallel by calling JavaScript.
  • the rendering unit 650 can include (not shown in FIG. 6):
  • a status setting subunit configured to set a request status for each resource request, where the request status is used to mark whether a corresponding target resource has been acquired
  • a module synthesizing subunit configured to: when the target resources are acquired according to the set request status, sequentially load the target resource according to the dependency relationship between the target resources, and synthesize the target HTML module;
  • a module adding unit configured to add the HTML module to the target DOM node to complete rendering of the target HTML module.
  • each HTML module of the HTML page includes:
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art are not creative In the case of labor, it can be understood and implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé, un dispositif et un appareil de restitution de page. Le procédé s'applique à un dispositif de client, et consiste : lors de la visite d'une page HTML par l'intermédiaire d'un navigateur, à traverser des nœuds DOM dans chaque module HTML dans la page HTML (101) ; lorsque la traversée s'effectue au niveau d'un nœud DOM cible dans un module HTML cible courant, à demander, en parallèle et selon des informations d'attribut définies dans le nœud DOM cible, à un serveur de multiples ressources cibles du module HTML cible (102) ; et à restituer le module HTML cible selon une relation entre les ressources cibles (103). Dans un mode de réalisation, la vitesse d'acquisition de ressource est accrue en demandant, en parallèle, toutes les ressources d'un module HTML par l'intermédiaire d'informations d'attribut prédéterminées de nœuds DOM durant la restitution de chaque module HTML d'une page HTML. En outre, après que toutes les ressources sont acquises, ces ressources peuvent être automatiquement chargées, permettant ainsi de réduire le temps de chargement de ressource, et d'améliorer la vitesse de restitution d'une page HTML en entier.
PCT/CN2016/095857 2015-08-31 2016-08-18 Procédé, dispositif et appareil de restitution de page WO2017036309A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510549439.4A CN106484383B (zh) 2015-08-31 2015-08-31 页面渲染方法、装置及设备
CN201510549439.4 2015-08-31

Publications (1)

Publication Number Publication Date
WO2017036309A1 true WO2017036309A1 (fr) 2017-03-09

Family

ID=58186685

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/095857 WO2017036309A1 (fr) 2015-08-31 2016-08-18 Procédé, dispositif et appareil de restitution de page

Country Status (2)

Country Link
CN (1) CN106484383B (fr)
WO (1) WO2017036309A1 (fr)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110322284A (zh) * 2019-06-14 2019-10-11 广州汇量信息科技有限公司 广告页面视图的展示方法及系统
CN111045655A (zh) * 2019-12-18 2020-04-21 广州市百果园信息技术有限公司 一种页面渲染的方法、装置、渲染服务器和存储介质
CN111221530A (zh) * 2020-01-08 2020-06-02 北京市科学技术情报研究所 移动端Web应用界面构建方法、Web应用界面及其操作方法
CN111258877A (zh) * 2018-11-30 2020-06-09 阿里巴巴集团控股有限公司 首屏页面可见时间的检测方法、装置及电子设备
CN111443921A (zh) * 2020-03-27 2020-07-24 中国平安财产保险股份有限公司 web前端项目的分包部署方法、系统和计算机设备
CN111880790A (zh) * 2020-06-12 2020-11-03 北京三快在线科技有限公司 页面渲染方法、页面渲染系统和计算机可读存储介质
CN111880860A (zh) * 2020-07-28 2020-11-03 北京浪潮数据技术有限公司 一种业务处理方法、装置及相关设备
CN111880788A (zh) * 2020-06-12 2020-11-03 北京三快在线科技有限公司 页面渲染方法、装置、客户端和计算机可读存储介质
CN112948011A (zh) * 2019-11-26 2021-06-11 上海哔哩哔哩科技有限公司 一种二级页面加载的方法及装置
CN113262469A (zh) * 2021-06-08 2021-08-17 网易（杭州）网络有限公司 一种资源模板的生成、游戏中场景元素的渲染方法及装置
CN113392350A (zh) * 2021-06-11 2021-09-14 中国联合网络通信集团有限公司 页面路由处理方法、装置、设备、存储介质及程序产品
CN113761412A (zh) * 2020-09-17 2021-12-07 北京沃东天骏信息技术有限公司 应用页面的显示方法、装置、电子设备、介质及应用系统
CN113760557A (zh) * 2020-05-29 2021-12-07 北京沃东天骏信息技术有限公司 页面数据的发送方法、装置、电子设备和存储介质
CN113760269A (zh) * 2020-07-17 2021-12-07 北京沃东天骏信息技术有限公司 配置方法和装置以及组件渲染方法、装置和系统
CN114237600A (zh) * 2021-12-20 2022-03-25 北京字节跳动网络技术有限公司 前端页面的代码生成方法、装置、设备以及存储介质
CN114911555A (zh) * 2022-04-19 2022-08-16 北京三快在线科技有限公司 页面显示方法、装置、电子设备及存储介质
CN116795405A (zh) * 2023-08-25 2023-09-22 苏州盈天地资讯科技有限公司 千人千面场景前端页面快速渲染方法、服务器及前端设备
CN116880901A (zh) * 2023-09-05 2023-10-13 国网思极网安科技（北京）有限公司 应用页面解析方法、装置、电子设备与计算机可读介质

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107169007B (zh) * 2017-03-31 2021-04-16 北京奇艺世纪科技有限公司 一种移动终端的显示界面设置方法及装置
CN107105336B (zh) * 2017-04-19 2021-01-08 腾讯科技（深圳）有限公司 数据处理方法及数据处理装置
CN107066430B (zh) * 2017-04-21 2021-02-26 阿里巴巴（中国）有限公司 图片处理方法、装置、服务端及客户端
CN107622106A (zh) * 2017-09-13 2018-01-23 五八有限公司 一种页面无法渲染时的提示方法及装置
CN109558186B (zh) * 2017-09-27 2022-06-28 阿里巴巴集团控股有限公司 一种页面显示方法和装置
WO2019071406A1 (fr) * 2017-10-10 2019-04-18 深圳中兴力维技术有限公司 Procédé de traitement d'internationalisation de première page, serveur d'applications et support de stockage lisible par ordinateur
CN109697266A (zh) * 2017-10-24 2019-04-30 中国电信股份有限公司 页面渲染系统、页面渲染方法及页面渲染装置
CN108595457A (zh) * 2017-12-29 2018-09-28 北京奇虎科技有限公司 一种瀑布流页面的渲染方法和装置
CN108322359A (zh) * 2018-01-08 2018-07-24 阿里巴巴集团控股有限公司 一种页面首屏时间的获取方法和装置
CN108595652A (zh) * 2018-04-27 2018-09-28 平安科技（深圳）有限公司 加载dom节点数据的方法、装置、计算机设备及存储介质
CN109002282B (zh) * 2018-07-26 2020-11-03 京东数字科技控股有限公司 一种在web页面开发中实现动画效果的方法和装置
CN111339548B (zh) * 2018-12-18 2023-11-03 北京京东尚科信息技术有限公司 反爬虫的数据处理方法、装置、计算机设备及存储介质
CN109865292B (zh) * 2019-01-10 2023-03-14 珠海金山数字网络科技有限公司 一种基于游戏引擎的游戏资源构建方法和装置
CN109902247B (zh) * 2019-02-14 2021-04-16 北京奇艺世纪科技有限公司 一种页面渲染的方法、装置及电子设备
CN110795195B (zh) * 2019-10-31 2023-09-26 百度在线网络技术（北京）有限公司 一种网页渲染方法、装置、电子设备及存储介质
CN111143732A (zh) * 2019-12-20 2020-05-12 贝壳技术有限公司 网页渲染方法及装置
CN113051874B (zh) * 2019-12-26 2023-12-26 阿里巴巴集团控股有限公司 一种用户行为数据渲染方法和装置
CN111310088B (zh) * 2020-02-12 2023-07-04 北京字节跳动网络技术有限公司 一种页面渲染方法及装置
CN111562918A (zh) * 2020-05-06 2020-08-21 中国银行股份有限公司 一种页面动态化生成方法及装置
CN111562919A (zh) * 2020-07-14 2020-08-21 成都市映潮科技股份有限公司 基于psd文件生成前端网页代码的方法、系统及存储介质
CN113315982B (zh) * 2021-05-07 2023-06-27 广州虎牙科技有限公司 一种直播方法、计算机存储介质及设备
CN113220366A (zh) * 2021-05-11 2021-08-06 北京达佳互联信息技术有限公司 子应用启动方法、装置、终端及服务器
CN115665480B (zh) * 2022-10-25 2024-06-07 广州至真信息科技有限公司 一种数据渲染方法、装置、计算机设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120278698A1 (en) * 2011-04-29 2012-11-01 International Business Machines Corporation Method and system for processing a webpage
CN102915375A (zh) * 2012-11-08 2013-02-06 山东大学 一种基于布局分区的网页加载方法
CN103593414A (zh) * 2013-10-29 2014-02-19 北京奇虎科技有限公司 一种浏览器中网页的展现方法和装置
CN104050190A (zh) * 2013-03-14 2014-09-17 腾讯科技（上海）有限公司 一种关系链数据处理的方法和系统、客户端

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8875032B2 (en) * 2008-05-08 2014-10-28 Dialogic Corporation System and method for dynamic configuration of components of web interfaces
CN103049439A (zh) * 2011-10-11 2013-04-17 腾讯科技（深圳）有限公司 标记语言文档的处理方法及浏览器和网络操作系统
US9898445B2 (en) * 2012-08-16 2018-02-20 Qualcomm Incorporated Resource prefetching via sandboxed execution
CN103679487B (zh) * 2012-09-05 2017-07-07 阿里巴巴集团控股有限公司 广告展示的监控方法和设备
CN104239441A (zh) * 2014-09-01 2014-12-24 可牛网络技术（北京）有限公司 网页加载控制方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120278698A1 (en) * 2011-04-29 2012-11-01 International Business Machines Corporation Method and system for processing a webpage
CN102915375A (zh) * 2012-11-08 2013-02-06 山东大学 一种基于布局分区的网页加载方法
CN104050190A (zh) * 2013-03-14 2014-09-17 腾讯科技（上海）有限公司 一种关系链数据处理的方法和系统、客户端
CN103593414A (zh) * 2013-10-29 2014-02-19 北京奇虎科技有限公司 一种浏览器中网页的展现方法和装置

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111258877A (zh) * 2018-11-30 2020-06-09 阿里巴巴集团控股有限公司 首屏页面可见时间的检测方法、装置及电子设备
CN111258877B (zh) * 2018-11-30 2023-05-02 阿里巴巴集团控股有限公司 首屏页面可见时间的检测方法、装置及电子设备
CN110322284A (zh) * 2019-06-14 2019-10-11 广州汇量信息科技有限公司 广告页面视图的展示方法及系统
CN112948011A (zh) * 2019-11-26 2021-06-11 上海哔哩哔哩科技有限公司 一种二级页面加载的方法及装置
CN112948011B (zh) * 2019-11-26 2023-08-08 上海哔哩哔哩科技有限公司 一种二级页面加载的方法及装置
CN111045655B (zh) * 2019-12-18 2023-04-14 广州市百果园信息技术有限公司 一种页面渲染的方法、装置、渲染服务器和存储介质
CN111045655A (zh) * 2019-12-18 2020-04-21 广州市百果园信息技术有限公司 一种页面渲染的方法、装置、渲染服务器和存储介质
CN111221530A (zh) * 2020-01-08 2020-06-02 北京市科学技术情报研究所 移动端Web应用界面构建方法、Web应用界面及其操作方法
CN111221530B (zh) * 2020-01-08 2023-11-14 北京市科学技术情报研究所 移动端Web应用界面构建方法、Web应用界面及其操作方法
CN111443921A (zh) * 2020-03-27 2020-07-24 中国平安财产保险股份有限公司 web前端项目的分包部署方法、系统和计算机设备
CN113760557A (zh) * 2020-05-29 2021-12-07 北京沃东天骏信息技术有限公司 页面数据的发送方法、装置、电子设备和存储介质
CN111880790A (zh) * 2020-06-12 2020-11-03 北京三快在线科技有限公司 页面渲染方法、页面渲染系统和计算机可读存储介质
CN111880788A (zh) * 2020-06-12 2020-11-03 北京三快在线科技有限公司 页面渲染方法、装置、客户端和计算机可读存储介质
CN113760269A (zh) * 2020-07-17 2021-12-07 北京沃东天骏信息技术有限公司 配置方法和装置以及组件渲染方法、装置和系统
CN111880860A (zh) * 2020-07-28 2020-11-03 北京浪潮数据技术有限公司 一种业务处理方法、装置及相关设备
CN113761412A (zh) * 2020-09-17 2021-12-07 北京沃东天骏信息技术有限公司 应用页面的显示方法、装置、电子设备、介质及应用系统
CN113262469A (zh) * 2021-06-08 2021-08-17 网易（杭州）网络有限公司 一种资源模板的生成、游戏中场景元素的渲染方法及装置
CN113392350B (zh) * 2021-06-11 2023-07-04 中国联合网络通信集团有限公司 页面路由处理方法、装置、设备及存储介质
CN113392350A (zh) * 2021-06-11 2021-09-14 中国联合网络通信集团有限公司 页面路由处理方法、装置、设备、存储介质及程序产品
CN114237600A (zh) * 2021-12-20 2022-03-25 北京字节跳动网络技术有限公司 前端页面的代码生成方法、装置、设备以及存储介质
CN114237600B (zh) * 2021-12-20 2023-08-11 抖音视界有限公司 前端页面的代码生成方法、装置、设备以及存储介质
CN114911555A (zh) * 2022-04-19 2022-08-16 北京三快在线科技有限公司 页面显示方法、装置、电子设备及存储介质
CN116795405A (zh) * 2023-08-25 2023-09-22 苏州盈天地资讯科技有限公司 千人千面场景前端页面快速渲染方法、服务器及前端设备
CN116795405B (zh) * 2023-08-25 2023-11-21 苏州盈天地资讯科技有限公司 千人千面场景前端页面快速渲染方法、服务器及前端设备
CN116880901A (zh) * 2023-09-05 2023-10-13 国网思极网安科技（北京）有限公司 应用页面解析方法、装置、电子设备与计算机可读介质
CN116880901B (zh) * 2023-09-05 2023-11-24 国网思极网安科技（北京）有限公司 应用页面解析方法、装置、电子设备与计算机可读介质

Also Published As

Publication number Publication date
CN106484383B (zh) 2019-08-23
CN106484383A (zh) 2017-03-08

Similar Documents

Publication Publication Date Title
WO2017036309A1 (fr) Procédé, dispositif et appareil de restitution de page
US11188353B2 (en) Runtime extension system for bundled web application
US10776564B2 (en) Method and system for displaying webpage self-defined content
US10242023B2 (en) Programming model for synchronizing browser caches across devices and web services
JP6051337B2 (ja) クライアント側ページ処理
US9178934B1 (en) Modifying web content at a client
US9875314B2 (en) Content request with HTTP request-header rendering template that is independent of content storage location
US9509764B1 (en) Updating cached web content
US9122658B2 (en) Webpage display system leveraging OSGi
CN110968824B (zh) 页面数据处理方法和装置
US9401949B1 (en) Client web content cache purge
US9075890B2 (en) Controller and method to build a combined web page using data retrieved from multiple APIs
US8682964B1 (en) Progressively loading network content
WO2016065969A1 (fr) Procédé et dispositif d'analyse du texte d'une page web, et terminal mobile
WO2019080796A1 (fr) Procédé, appareil et dispositif de séparation de premier plan et d'arrière-plan d'un système web, et support de stockage
CN110471657A (zh) 网站页面的生成方法及装置
US20170017380A1 (en) Mobile enabling a web application developed without mobile rendering capabilities
GB2539758A (en) Techniques for evaluating applications through use of an auxiliary application
CN112930530B (zh) 用于网络应用程序执行的客户端应用程序
CN111079048B (zh) 一种页面加载方法及装置
WO2021087858A1 (fr) Migration de composant d'application web vers un système infonuagique
US20180084043A1 (en) System and method providing local development of executable content pages normally run on a server within a user session
US20120151313A1 (en) User-specific customization of web pages
US20170262550A1 (en) Caching of a site model in a hierarchical modeling system for network sites
US10530709B2 (en) Container contract for data dependencies

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16840738

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16840738

Country of ref document: EP

Kind code of ref document: A1