CN110750255A - Applet rendering method and device - Google Patents
Applet rendering method and device Download PDFInfo
- Publication number
- CN110750255A CN110750255A CN201910911166.1A CN201910911166A CN110750255A CN 110750255 A CN110750255 A CN 110750255A CN 201910911166 A CN201910911166 A CN 201910911166A CN 110750255 A CN110750255 A CN 110750255A
- Authority
- CN
- China
- Prior art keywords
- applet
- module
- request
- rendering
- browser
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The specification provides an applet rendering method and device, wherein the method comprises the following steps: loading a local access address of an applet package to be rendered on a target page opened by a non-interface browser to acquire and operate the applet package; intercepting a frame code request sent by the target page through a browser communication control module, wherein the frame code request is used for requesting to load an applet frame code; returning a local framework code to the framework code request, and loading and running the local framework code; and controlling the page rendering of the applet through a communication bridge module arranged in the target page, wherein the communication bridge module is used for being responsible for the communication of the applet.
Description
Technical Field
The present disclosure relates to data processing technologies, and in particular, to a method and an apparatus for rendering an applet.
Background
The applet is a brand new open mode, can be conveniently acquired and propagated, and provides a better user experience for the terminal user. In the development of the small program, the content safety of the small program is also ensured, and the quality risk prevention and control of the small program content is an important work. The small program runs on the client, and if the quality risk prevention and control of the small program is carried out on the server, how to realize the rendering of the small program on the server is a problem to be solved.
Disclosure of Invention
In view of this, at least one embodiment of the present disclosure provides an applet rendering method and apparatus to achieve applet rendering at a server side with low cost.
Specifically, the description is realized by the following technical scheme:
in a first aspect, a method for rendering an applet is provided, the method comprising:
loading a local access address of an applet package to be rendered on a target page opened by a non-interface browser to acquire and operate the applet package;
intercepting a frame code request sent by the target page through a browser communication control module, wherein the frame code request is used for requesting to load an applet frame code;
returning a local framework code to the framework code request, and loading and running the local framework code;
and controlling the page rendering of the applet through a communication bridge module arranged in the target page, wherein the communication bridge module is used for being responsible for the communication of the applet.
In a second aspect, there is provided an applet rendering apparatus, the apparatus comprising:
the system comprises an initial loading module, a rendering module and a rendering module, wherein the initial loading module is used for loading a local access address of an applet package to be rendered on a target page opened by a non-interface browser so as to acquire and operate the applet package;
the frame acquisition module is used for intercepting a frame code request sent by the target page through the browser communication control module, wherein the frame code request is used for requesting to load an applet frame code;
the frame loading module is used for requesting the frame code to return a local frame code and loading and operating the local frame code;
and the rendering processing module is used for controlling the page rendering of the applet through a communication bridge module arranged in the target page, and the communication bridge module is used for being responsible for the communication of the applet.
In a third aspect, an applet rendering apparatus is provided, the apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the applet rendering method according to any one of the embodiments of the present description when executing the program.
According to the applet rendering method and device provided by at least one embodiment of the specification, the server-side rendering of the applet is realized by using the technical scheme that the server can run; and the non-interface operation of the small program at the server side is realized by using the non-interface browser, so that the online safety risk is reduced.
Drawings
FIG. 1 is a browser preparation workflow provided in at least one embodiment of the present description;
FIG. 2 is a block diagram of a framework code request provided in at least one embodiment of the present specification;
FIG. 3 is a schematic diagram of an applet communication provided in at least one embodiment of the present description;
FIG. 4 is a detailed architecture diagram of an applet communication provided in at least one embodiment of the present description;
FIG. 5 is a diagram of an applet rendering method provided in at least one embodiment of the specification;
fig. 6 is a block diagram of an applet rendering apparatus according to at least one embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The purpose of the embodiments of the present disclosure is to provide a method for rendering an applet at a server, which achieves the applet rendering at the server, so that the applet page content can be captured to perform security prevention and control on the applet content. For example, applet rendering may be performed at a Linux-based server. Moreover, by the method provided by the embodiment of the present specification, when the servlet renders an applet, the method may not depend on a display device, which includes, but is not limited to: a display, a graphics card, a device with an interface, a graphics card simulator, etc.
The method for realizing the server rendering of the small program can comprise the following four steps: applet build package preparation, browser preparation, applet environment preparation and applet execution.
The detailed description is as follows:
1) applet build package preparation
The small program building package is a small program package to be rendered, and the small program package is consistent with a client access package of the small program when the client runs, so that the rendered small program page is the same as the small program page seen by a user when the client runs.
The applet package may be placed at a local access address, which may be some locally specified address of the server. For example, the locally specified address may be http://127.0.0.1:8000/index. html, and Local static resource service (Local Server) is opened for the applet package at the locally specified address. So that subsequent browsers can access the address to load the running applet package.
2) Browser preparation
The browser used in the embodiment can be an interface-free browser, a visual interface is not needed when the server side runs, and the implementation cost can be reduced by adopting the interface-free browser to run. For example, a Headless chrome browser may be used, running the chrome browser without displaying an interface.
Referring to the flow of fig. 1, browser preparation is described as follows:
in step 100, a page of the browser is opened.
For example, a read resolution browser may be opened via a CDP (color DevTools protocol) command, which may also be referred to as a remote debugging protocol, and a new Page in the browser is opened, where the new Page may be identified by a Page and may be referred to as a target Page. The CDP command is a communication protocol for remotely controlling Chrome/Chrome behavior, and may be used for operations such as opening a browser, opening a page, intercepting a request, and retrieving page content. The module that executes the CDP command may also be referred to as a browser communication control module.
In step 102, a communication bridge module is injected in the page.
In this step, a Bridge module, which is a Bridge for communicating the applet framework (af-appx) to the outside, may be injected into the JS environment of the page, and used in the step of running the subsequent applet. The Bridge module may be referred to as a communication bridging module.
In step 104, an access address of the applet package is opened in the page to load the running applet package.
In this step, http://127.0.0.1:8000/index.html of the access address can be opened in the page, so as to obtain the applet package through the address and load and run the applet package. The applet package may include files such as index.
3) Applet environment preparation
The environment preparation in this step is mainly to load the frame code of the applet frame in the target page, and the applet frame can be used for the running management of the applet. This process belongs to the process of applet initialization.
The framework code of the applet may also include a plurality of code portions, and correspondingly, different code portions are requested by a plurality of framework code requests.
For example, referring to the illustration of fig. 2, an applet may run a thread that requests an af-appx.js in the framework code via a framework code request (NetworkRequest request). The applet may also run another thread that also requests, via a framework code request (NetworkRequest request), af-appx. I.e. different frame code requests are executed by a plurality of threads, respectively.
In this embodiment, the browser may intercept, through a command of the browser communication control module CDP, a frame code request for requesting to load an applet frame code, which is sent by a target page of the applet.
For example, the above-described process of requesting applet framework code may be such that: injecting the Bridge module into the JS environment of the page has two derivatives of different environments, one is a Worker in the Render, and the embodiment is WebWorker. For the Bridge operating environment in the Render is the normal Render environment of the browser, the Bridge in the Worker is under the WebWorker environment. Both Render and WebWorker will send requests for applet frames appx, Render sends requests for af-appx. The browser communication control module can intercept the requests through CDP commands.
As above, the browser communication control module in Render may be referred to as a first control unit, and the browser communication control module in WebWorker may be referred to as a second control unit; af-appx.js is called a first framework code, and af-appx.worker.js is called a second framework code. That is, the first control unit intercepts a request for requesting a first frame code sent by a target page, and the second control unit intercepts a request for a second frame code sent by the target page.
After interception, a local substitution script is returned to the framework code request, the local substitution script can be called as a local framework code, the applet framework can be run after the local framework code is run, only the NetworkRequest request is to obtain the framework code to the outside, and the framework code of the embodiment is put in a server to be obtained locally. This speeds up the loading of the applet.
In addition, the applet business code execution thread is realized by WebWorker. A NetworkRequest request requesting af-appx. The WebWorker is a worker carried by a non-interface browser, and can also intercept requests by executing CDP commands.
It should be noted that, in preparation before the applet runs, or in the applet runs, the service code execution environment involved may be simulated by using webWorker in the self-contained interface browser. The browser is low in cost, can be communicated with a CDP command, and can execute request interception, JS script injection and the like through the CDP command.
In other implementations, the service code execution environment may be replaced by child process of nodjs, but the execution context needs to complement the variables and methods that exist in WebWorker such as importscript and fetch. In addition, the service worker of the non-interface browser has the problem that the communication with the CDP command cannot be realized, and the resource interception is obstructed.
In this step, after the frame code is acquired, the local frame code is loaded to run the applet frame.
4) Applet running
After the initialization process is complete, the applet can begin executing the business logic process.
In this step, the applet can communicate with the outside to acquire the applet page content and realize the applet rendering. Wherein the communication Bridge module Bridge can be responsible for the communication of the applet with the outside world. For example, FIG. 3 illustrates external communication by the Bridge module controlling the applet.
Fig. 4 is a schematic diagram of a detailed architecture of communication between an applet controlled by a Bridge module and the outside world, and as shown in fig. 4, a browser, loaded into an applet package, may include two types of codes, which are respectively run in a worker (webworker) and a render rendering layer, which may be referred to as a worker and a render as follows. The worker runs the logic processing code of the applet, including event handling, API calls and lifecycle management of the framework. The render runs the rendering code of the applet, mainly comprises a template/style and a cross-terminal js component of the framework, acquires the data of the logic layer, and operates a rendering engine (the applet framework) to render. The worker and the render can establish connection, data needing rendering is transmitted to the corresponding render to be rendered, the render sends the triggering event of the component to the corresponding worker to be processed, and meanwhile setData of the worker can be received to call the small program framework to be rendered again.
With continued reference to fig. 4, the communication Bridge module Bridge of the present embodiment may include two customized bridges, which are located in the worker and the render, respectively. Both the render and the worker may initiate jsapi requests, and both the render and the worker may first pass through an applet framework (af-appx, af-appx. worker), and then forward to a Bridge module (the Bridge module has functions of both the render and the worker and receiving and sending jsapi), and then forward information to the Bridge call on the node js side, and the Bridge module processes various jsapis in a centralized manner.
When the applet is to communicate with the outside world, for example, the service logic code in the worker requests another server to obtain the content of the applet page, the service logic code may instruct the applet framework to encapsulate a service request, and the service request of the applet framework is further format-encapsulated by the Bridge module and then sent to the Bridge in the nodjs for processing, for example, sending the request to the outside world server.
One example is as follows: the applet service logic code determines that the user information is to be obtained from an external server, and the applet framework (appx) generates a service request my. As shown in fig. 4, the applet framework sends the request to the customized Bridge module in the worker, and the customized Bridge module is further encapsulated as jsbridge.call (getUserInfo) according to the request, and performs communication processing based on the encapsulated service request to obtain the applet page content corresponding to the service request, for example, sending the encapsulated service request to nodejs (Bridge call). The nodesjs (bridge call) may call a corresponding API, generate rpc.request ('getUserInfo') according to the request, and request an external server to obtain user information, where the user information is equivalent to the applet page content. After the outside world returns the user information, the NodeJS returns the user information to the worker, and the user information is interactively transmitted to the render by the Bridge module in the worker and the render. Of course, in the non-interface browser, rendering by render is not visually displayed.
Similarly, other communications involving the applet communicating with the outside world, or between the renderer and the worker of the applet, are facilitated by the Bridge module. The "Bridge module" includes the ability to customize Bridge to various types of APIs according to the communication requirements of the applet framework af-appx to target normal applet communication.
In addition, the above example is taken as an example that the applet obtains page user information from an external server, and in other implementation manners, some of the communication requests from the applet to the external server relate to an authorization process related to the user, for example, the user is required to select some options, or the user provides some input information, and the request result can be returned through customization by Bridge.
For example, referring to fig. 4, bridge call in nodjs, upon receiving some external communication request involving user authorization, may call a corresponding API interface that can directly return customized results, which may be a simulation of the user's response to some information.
And completing the applet rendering of the server through the four steps. After the applet page is acquired in the rendering process, the applet page content can be extracted through a CDP command so as to perform security detection or other applications. The specific extracted applet content may be determined according to actual business requirements.
According to the above description, the applet rendering method provided in this specification is obtained as shown in fig. 5:
in step 500, a local access address of an applet package to be rendered is loaded on a target page opened by a non-interface browser to obtain and run the applet package.
In the step, a page is opened in the non-interface browser, the applet package is loaded and operated on the page, and a communication bridging module responsible for the external communication of the applet is injected into the page.
In step 502, a frame code request sent by the target page is intercepted by a browser communication control module, and the frame code request is used for requesting to load an applet frame code.
In step 504, a local framework code is returned to the framework code request, and the local framework code is loaded and run.
In step 506, the applet page rendering is controlled through a communication bridge module arranged in the target page, wherein the communication bridge module is used for being responsible for communication of the applet.
According to the applet rendering method, the technical scheme that Linux servers such as JavaScript, Nodejs and chrome can run is used, so that the server rendering of the applet is realized; and the non-interface operation of the small program at the server side is realized by using the non-interface browser, so that the online safety risk is reduced. The method also uses WebWorker as an implementation scheme of an applet service code execution environment, communication with an applet frame (Appx) frame is completed through a customized Bridge module, a CDP command is used for intercepting network requests, resource injection and redirection, normal applet rendering is ensured, and loading efficiency is accelerated; and a Bridge module is also used for customizing a return result to ensure the normal operation of the non-interface mode.
Fig. 6 is a schematic structural diagram of an applet rendering apparatus provided in at least one embodiment of the present specification, where the apparatus may perform the applet rendering method according to any one embodiment of the present specification.
As shown in fig. 6, the apparatus may include: an initial loading module 61, a frame acquisition module 62, a frame loading module 63, and a rendering processing module 64.
The initial loading module 61 is configured to load a local access address of an applet package to be rendered on a target page opened by a non-interface browser, so as to obtain and run the applet package;
a frame obtaining module 62, configured to intercept, by a browser communication control module, a frame code request sent by the target page, where the frame code request is used to request to load an applet frame code;
the frame loading module 63 is configured to request the frame code to return a local frame code, and load and run the local frame code;
and a rendering processing module 64, configured to control applet page rendering through a communication bridge module set in the target page, where the communication bridge module is used for controlling applet page rendering.
In one example, the browser communication control module includes: the control system comprises a first control unit running in a Render and a second control unit running in a WebWorker; the applet framework code comprising: a first frame code and a second frame code;
the frame obtaining module 62, when configured to intercept a frame code request sent by a target page through the browser communication control module, includes: intercepting a request for the first frame code sent by the target page through a first control unit in a browser communication control module; and intercepting a request for the second frame code sent by the target page through a second control unit in a browser communication control module.
In an example, the rendering processing module 64 is specifically configured to: and encapsulating the service request of the applet framework through the communication bridging module, and executing communication processing based on the encapsulated service request to acquire the applet page content corresponding to the service request.
In one example, the rendering processing module 64, when used to control applet page rendering, comprises: and returning a customized request result for the service request of the applet, wherein the request result is used for simulating the response of the user to the service request.
In one example, the rendering processing module 64 is further configured to extract applet page content through the browser communication control module.
At least one embodiment of the present specification further provides an applet rendering apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the applet rendering method according to any one of the embodiments of the specification when executing the program.
At least one embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, can implement processing steps in the applet rendering method described in any one of the embodiments of the specification, or can implement processing steps of the applet rendering method described in any one of the embodiments of the specification.
The execution sequence of each step in the flow shown in the above method embodiment is not limited to the sequence in the flowchart. Furthermore, the description of each step may be implemented in software, hardware or a combination thereof, for example, a person skilled in the art may implement it in the form of software code, and may be a computer executable instruction capable of implementing the corresponding logical function of the step. When implemented in software, the executable instructions may be stored in a memory and executed by a processor in the device.
The apparatuses or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, the functionality of the modules may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description 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.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
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.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the data acquisition device or the data processing device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (13)
1. A method of applet rendering, the method comprising:
loading a local access address of an applet package to be rendered on a target page opened by a non-interface browser to acquire and operate the applet package;
intercepting a frame code request sent by the target page through a browser communication control module, wherein the frame code request is used for requesting to load an applet frame code;
returning a local framework code to the framework code request, and loading and running the local framework code;
and controlling the page rendering of the applet through a communication bridge module arranged in the target page, wherein the communication bridge module is used for being responsible for the communication of the applet.
2. The method of claim 1, before loading the local access address of the applet to be rendered at the target page of the non-interface browser open, the method further comprising:
acquiring the small program package to be rendered, wherein the small program package is consistent with a client access package;
and starting local static resource service on the small program package at a local access address, so that the small program package is loaded by accessing the local access address on the target page of the non-interface browser.
3. The method of claim 1, the browser communication control module comprising: the control system comprises a first control unit running in a Render and a second control unit running in a WebWorker; the applet framework code comprising: a first frame code and a second frame code;
the intercepting of the frame code request sent by the target page through the browser communication control module comprises the following steps: the first control unit intercepts a request for the first frame code sent by the target page; the second control unit intercepts a request for the second frame code sent by the target page.
4. The method of claim 3, the first framework code being af-appx.js; the second framework code is af-appx. The WebWorker is a Worker with an interface-free browser.
5. The method of claim 1, the controlling applet page rendering by a communication bridge module provided in the target page, comprising:
packaging the service request of the applet framework through the communication bridging module;
and executing communication processing based on the encapsulated service request to acquire the small program page content corresponding to the service request.
6. The method of claim 1, the controlling applet page rendering by a communication bridge module provided in the target page, comprising: and returning a customized request result for the service request of the applet, wherein the request result is used for simulating the response of the user to the service request.
7. The method of claim 1, further comprising: and extracting the page content of the applet through the browser communication control module.
8. An applet rendering apparatus, the apparatus comprising:
the system comprises an initial loading module, a rendering module and a rendering module, wherein the initial loading module is used for loading a local access address of an applet package to be rendered on a target page opened by a non-interface browser so as to acquire and operate the applet package;
the frame acquisition module is used for intercepting a frame code request sent by the target page through the browser communication control module, wherein the frame code request is used for requesting to load an applet frame code;
the frame loading module is used for requesting the frame code to return a local frame code and loading and operating the local frame code;
and the rendering processing module is used for controlling the page rendering of the applet through a communication bridge module arranged in the target page, and the communication bridge module is used for being responsible for the communication of the applet.
9. The apparatus of claim 8, the browser communication control module comprising: the control system comprises a first control unit running in a Render and a second control unit running in a WebWorker; the applet framework code comprising: a first frame code and a second frame code;
the frame obtaining module, when being used for intercepting a frame code request sent by a target page through the browser communication control module, comprises: intercepting a request for the first frame code sent by the target page through a first control unit in a browser communication control module; and intercepting a request for the second frame code sent by the target page through a second control unit in a browser communication control module.
10. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,
the rendering processing module is specifically configured to: and encapsulating the service request of the applet framework through the communication bridging module, and executing communication processing based on the encapsulated service request to acquire the applet page content corresponding to the service request.
11. The apparatus of claim 8, the rendering processing module, when used to control applet page rendering, comprising: and returning a customized request result for the service request of the applet, wherein the request result is used for simulating the response of the user to the service request.
12. The apparatus of claim 8, the rendering processing module further to extract applet page content through the browser communication control module.
13. An applet rendering apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the applet rendering method according to any one of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910911166.1A CN110750255B (en) | 2019-09-25 | 2019-09-25 | Applet rendering method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910911166.1A CN110750255B (en) | 2019-09-25 | 2019-09-25 | Applet rendering method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750255A true CN110750255A (en) | 2020-02-04 |
| CN110750255B CN110750255B (en) | 2022-08-02 |
Family
ID=69277014
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910911166.1A Active CN110750255B (en) | 2019-09-25 | 2019-09-25 | Applet rendering method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750255B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414525A (en) * | 2020-03-25 | 2020-07-14 | 深圳市腾讯网域计算机网络有限公司 | Data acquisition method and device for small program, computer equipment and storage medium |
| CN111475259A (en) * | 2020-04-02 | 2020-07-31 | 北京百度网讯科技有限公司 | Applet loading method and device and electronic equipment |
| CN112257060A (en) * | 2020-11-12 | 2021-01-22 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment |
| CN112631689A (en) * | 2021-01-04 | 2021-04-09 | 北京字节跳动网络技术有限公司 | Application program loading method and device and computer storage medium |
| CN113315822A (en) * | 2021-05-21 | 2021-08-27 | 福建天泉教育科技有限公司 | Page staticizing method and system under front-end and back-end separation framework |
| WO2022152142A1 (en) * | 2021-01-14 | 2022-07-21 | 钉钉控股（开曼）有限公司 | Generation method for virtual card, and interaction implementation method and apparatus for virtual card |
| WO2023169157A1 (en) * | 2022-03-08 | 2023-09-14 | 腾讯科技（深圳）有限公司 | Sub application running method and apparatus, electronic device, program product, and storage medium |
| CN117170883A (en) * | 2023-11-02 | 2023-12-05 | 西安芯云半导体技术有限公司 | Method, device, equipment and storage medium for rendering display |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103412890A (en) * | 2013-07-19 | 2013-11-27 | 北京亿赞普网络技术有限公司 | Webpage loading method and device |
| US8626919B1 (en) * | 2008-11-07 | 2014-01-07 | Google Inc. | Installer-free applications using native code modules and persistent local storage |
| CN104850560A (en) * | 2014-02-18 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Method and system for loading business data in webpage in real time |
| CN106354700A (en) * | 2016-08-11 | 2017-01-25 | 广州爱九游信息技术有限公司 | Page text conversion method and system |
| CN108984170A (en) * | 2017-06-02 | 2018-12-11 | 阿里巴巴集团控股有限公司 | The multilingual rendering method of the H5 page and device |
| CN109375918A (en) * | 2018-11-23 | 2019-02-22 | 天津字节跳动科技有限公司 | Interface rendering method, device, electronic equipment and the storage medium of small routine |
| US20190065157A1 (en) * | 2017-08-30 | 2019-02-28 | Salesforce.Com, Inc. | Web application builder framework |
| CN109656670A (en) * | 2018-12-27 | 2019-04-19 | 广州华多网络科技有限公司 | A kind of page rendering method and device |
-
2019
- 2019-09-25 CN CN201910911166.1A patent/CN110750255B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8626919B1 (en) * | 2008-11-07 | 2014-01-07 | Google Inc. | Installer-free applications using native code modules and persistent local storage |
| CN103412890A (en) * | 2013-07-19 | 2013-11-27 | 北京亿赞普网络技术有限公司 | Webpage loading method and device |
| CN104850560A (en) * | 2014-02-18 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Method and system for loading business data in webpage in real time |
| CN106354700A (en) * | 2016-08-11 | 2017-01-25 | 广州爱九游信息技术有限公司 | Page text conversion method and system |
| CN108984170A (en) * | 2017-06-02 | 2018-12-11 | 阿里巴巴集团控股有限公司 | The multilingual rendering method of the H5 page and device |
| US20190065157A1 (en) * | 2017-08-30 | 2019-02-28 | Salesforce.Com, Inc. | Web application builder framework |
| CN109375918A (en) * | 2018-11-23 | 2019-02-22 | 天津字节跳动科技有限公司 | Interface rendering method, device, electronic equipment and the storage medium of small routine |
| CN109656670A (en) * | 2018-12-27 | 2019-04-19 | 广州华多网络科技有限公司 | A kind of page rendering method and device |
Non-Patent Citations (2)
| Title |
|---|
| 刘望舒: "支付宝app架构的原理与实践", 《HTTPS://WWW.SOHU.COM/A/341358883_100004247》 * |
| 老章888: "支付宝小程序技术历程-框架概述", 《HTTPS://WWW.JIANSHU.COM/P/9F040D2CF230》 * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414525A (en) * | 2020-03-25 | 2020-07-14 | 深圳市腾讯网域计算机网络有限公司 | Data acquisition method and device for small program, computer equipment and storage medium |
| CN111414525B (en) * | 2020-03-25 | 2024-01-02 | 深圳市腾讯网域计算机网络有限公司 | Method, device, computer equipment and storage medium for acquiring data of applet |
| CN111475259A (en) * | 2020-04-02 | 2020-07-31 | 北京百度网讯科技有限公司 | Applet loading method and device and electronic equipment |
| CN112257060A (en) * | 2020-11-12 | 2021-01-22 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment |
| CN112631689A (en) * | 2021-01-04 | 2021-04-09 | 北京字节跳动网络技术有限公司 | Application program loading method and device and computer storage medium |
| WO2022152142A1 (en) * | 2021-01-14 | 2022-07-21 | 钉钉控股（开曼）有限公司 | Generation method for virtual card, and interaction implementation method and apparatus for virtual card |
| CN113315822A (en) * | 2021-05-21 | 2021-08-27 | 福建天泉教育科技有限公司 | Page staticizing method and system under front-end and back-end separation framework |
| CN113315822B (en) * | 2021-05-21 | 2023-06-20 | 福建天泉教育科技有限公司 | Page staticizing method and system under front-end and back-end separation architecture |
| WO2023169157A1 (en) * | 2022-03-08 | 2023-09-14 | 腾讯科技（深圳）有限公司 | Sub application running method and apparatus, electronic device, program product, and storage medium |
| CN117170883A (en) * | 2023-11-02 | 2023-12-05 | 西安芯云半导体技术有限公司 | Method, device, equipment and storage medium for rendering display |
| CN117170883B (en) * | 2023-11-02 | 2024-01-30 | 西安芯云半导体技术有限公司 | Method, device, equipment and storage medium for rendering display |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750255B (en) | 2022-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110750255B (en) | Applet rendering method and device | |
| CN110795195B (en) | Webpage rendering method and device, electronic equipment and storage medium | |
| EP2339465B1 (en) | Location independent execution of user interface operations | |
| CN107203419A (en) | Intermodule call method, apparatus and system in application program | |
| CN105718313A (en) | Application operation method and device | |
| CN108304234B (en) | Page display method and device | |
| WO2014150045A1 (en) | Switching to and from native web applications | |
| US9678814B2 (en) | Implementing a java method | |
| US11023558B1 (en) | Executing functions on-demand on a server utilizing web browsers | |
| WO2017189644A1 (en) | Hosting apps with native capabilities | |
| US10198279B2 (en) | Thread synchronization for platform neutrality | |
| CN112256421A (en) | Communication processing method, communication processing device, storage medium and electronic equipment | |
| CN111078325B (en) | Application program running method and device, electronic equipment and storage medium | |
| US10089406B2 (en) | Generating web pages with integrated content | |
| CN107517188A (en) | A kind of data processing method and device based on Android system | |
| CN109725887B (en) | Data interaction method and device based on message research and development framework and terminal equipment | |
| CN108509228B (en) | Page loading method, terminal equipment and computer readable storage medium | |
| CN112764746A (en) | Data processing method and device, electronic equipment and storage medium | |
| JP2006276939A (en) | Program starting method for virtual machine, and client server system | |
| CN113315829B (en) | Client offline H5 page loading method and device, computer equipment and medium | |
| KR101739854B1 (en) | Computational science open platform, test system and method | |
| CN114860205A (en) | Application extension system, method and device of low-code development platform | |
| CN111104183B (en) | Application program running method and device, electronic equipment and storage medium | |
| CN107391354A (en) | The method and system of automatic monitoring terminal performance, storage device | |
| CN112667490A (en) | Performance test method and device based on hook function |
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: 40023005 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |