CN107743266B - Flash and JS page efficient rendering communication method, storage medium, device and system - Google Patents

Flash and JS page efficient rendering communication method, storage medium, device and system Download PDF

Info

Publication number
CN107743266B
CN107743266B CN201710932695.0A CN201710932695A CN107743266B CN 107743266 B CN107743266 B CN 107743266B CN 201710932695 A CN201710932695 A CN 201710932695A CN 107743266 B CN107743266 B CN 107743266B
Authority
CN
China
Prior art keywords
data
page
server
flash
cache pool
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
Application number
CN201710932695.0A
Other languages
Chinese (zh)
Other versions
CN107743266A (en
Inventor
潘龙
陈少杰
张文明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wuhan Douyu Network Technology Co Ltd
Original Assignee
Wuhan Douyu Network Technology Co Ltd
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 Wuhan Douyu Network Technology Co Ltd filed Critical Wuhan Douyu Network Technology Co Ltd
Priority to CN201710932695.0A priority Critical patent/CN107743266B/en
Priority to PCT/CN2017/117382 priority patent/WO2019071830A1/en
Publication of CN107743266A publication Critical patent/CN107743266A/en
Application granted granted Critical
Publication of CN107743266B publication Critical patent/CN107743266B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/44Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs
    • H04N21/44004Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs involving video buffer management, e.g. video decoder buffer or video display buffer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44209Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/4424Monitoring of the internal components or processes of the client device, e.g. CPU or memory load, processing speed, timer, counter or percentage of the hard disk space used
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81Monomedia components thereof
    • H04N21/8166Monomedia components thereof involving executable data, e.g. software
    • H04N21/8173End-user applications, e.g. Web browser, game

Abstract

The invention discloses a method, a storage medium, equipment and a system for efficient rendering communication of Flash and JS (JavaScript) pages, and relates to the technical field of Flash live broadcast development. The method comprises the following steps: creating and initializing a data cache pool; establishing Socket connection between a Flash player and a server, and setting event monitoring; once the server is monitored to send data, the data of the server is received and stored in a data cache pool; monitoring a frame frequency event at the bottom layer of the Flash player, and dividing data in a current data cache pool into N parts and sending the N parts to a JS page by using an IO data interface once the frame frequency event is monitored; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page. The method and the device can solve the problem of performance bottleneck caused by a large amount of communication between the Flash player and the JS page in the rendering process, so that rendered pictures have no pause and pause feeling, and the user experience is good.

Description

Flash and JS page efficient rendering communication method, storage medium, device and system
Technical Field
The invention relates to the technical field of Flash live broadcast development, in particular to a communication method, a storage medium, equipment and a system for efficient rendering of Flash and JS pages.
Background
At present, a large-scale domestic live broadcast platform basically uses a Flash player and JS page mixed and matched scheme to construct a web-side live broadcast platform. The advantages of adopting the mixing scheme are that: the embarrassment that JS cannot use Socket to communicate in time is avoided, and the problem that JS uses webSocket (which is a new protocol of HTML5 and realizes full-duplex communication between a browser and a server) to communicate with the server in time is avoided (because the content of webSocket communication information is plaintext and can be directly cut off).
However, in the existing mashup scheme, a Flash player is adopted as a middle key of a communication layer: when the Flash player receives the message sent by the server, a page IO (Input/Output) interface is called to transmit the message to the JS page. In this way, the Flash player needs to play the video and render its own service, and also needs to be used as a middle key for communicating with the JS page and the server, which makes the overall communication performance very low. Particularly, in the rendering process of a Flash player, because the existing rendering operation is not a rendering mode based on a bottom layer but a rendering mode based on a business logic layer, the rendering efficiency can cause the performance bottleneck problem due to a large amount of communication between the Flash player and a JS page (in the existing mixing and assembling scheme, an IO interface is directly called when data which needs to be transmitted to the JS page is received every time, and thus the performance is limited when the number of times of calling the IO interface is large within a certain time), so that a rendered picture has a pause feeling and the user experience is poor.
Disclosure of Invention
The invention aims to overcome the defects of the background technology, and provides a Flash and JS page efficient rendering communication method, a storage medium, equipment and a system, which can solve the problem of performance bottleneck caused by a large amount of communication between a Flash player and a JS page in the rendering process, so that rendered pictures have no pause and pause feeling, and the user experience is good.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows: the method for the efficient rendering communication of the Flash and the JS page is provided, and comprises the following operations:
establishing and initializing a data cache pool, wherein the data cache pool is used for caching data received by a Flash player from a server;
establishing Socket connection between the Flash player and the server, and setting an event monitor for monitoring whether the server has data sent;
once the server is monitored to send data, the data of the server is received and stored in a data cache pool;
monitoring a frame frequency event at the bottom layer of the Flash player, dividing data in a current data cache pool into N parts and sending the N parts to a JS page for N times by using an IO data interface which is appointed with the JS page and is used for receiving the transmission of the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page.
On the basis of the technical scheme, the concrete operations of establishing the Socket connection between the Flash player and the server and setting an event monitoring for monitoring whether the server has data sent are as follows: instantiating a Socket object in the Flash player, setting a server IP (Internet protocol) required to be connected and a server post parameter required to be connected, and establishing Socket connection with a server; and then setting an event monitor for monitoring whether the server has data to send.
On the basis of the technical scheme, if the number of the data in the current data cache pool is less than N, one data in the current data cache pool is sent to the JS page.
On the basis of the technical scheme, the current data cache pool is emptied after the data in the current data cache pool is divided into N parts and sent to the JS page for N times.
The invention also provides a storage medium, wherein a computer program is stored on the storage medium, and when the computer program is executed by a processor, the steps of the Flash and JS page efficient rendering communication method are realized.
The invention also provides a Flash and JS page efficient rendering communication device which comprises a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor realizes the Flash and JS page efficient rendering communication method when executing the computer program.
The invention also provides a Flash and JS page efficient rendering communication system, which comprises a data cache pool establishing module, a server connecting and monitoring setting module, a data cache module and a rendering communication processing module;
the data cache pool creation module is configured to: establishing and initializing a data cache pool, wherein the data cache pool is used for caching data received by a Flash player from a server;
the server connecting and monitoring setting module is used for: establishing Socket connection between the Flash player and the server, and setting an event monitor for monitoring whether the server has data sent;
the data caching module is used for: once the server is monitored to send data, the data of the server is received and stored in a data cache pool;
the rendering communication processing module is used for: monitoring a frame frequency event at the bottom layer of the Flash player, dividing data in a current data cache pool into N parts and sending the N parts to a JS page for N times by using an IO data interface which is appointed with the JS page and is used for receiving the transmission of the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page.
On the basis of the technical scheme, the server connection and monitoring setting module establishes Socket connection between the Flash player and the server, and sets a specific operation for monitoring whether the server has event monitoring sent by data to be: instantiating a Socket object in the Flash player, setting a server IP (Internet protocol) required to be connected and a server post parameter required to be connected, and establishing Socket connection with a server; and then setting an event monitor for monitoring whether the server has data to send.
On the basis of the technical scheme, if the number of the data in the current data cache pool is less than N, the rendering communication processing module sends one piece of data in the current data cache pool to the JS page.
On the basis of the technical scheme, the rendering communication processing module divides the data in the current data cache pool into N parts and sends the N parts to the JS page, and then the current data cache pool is emptied.
The invention has the beneficial effects that:
(1) according to the invention, the data in the current data cache pool is divided into N parts and sent to the JS page in N times instead of sending to the JS page at one time, so that the problems that the data is very large due to single IO operation when the data amount in the data cache pool is too much, the page consumption is increased, and the overall processing efficiency is reduced can be solved. And the value range of N is set to be not more than 10, namely, the value range is sent once in 1 millisecond, so that the peak value of data communication can be reduced, and the picture can be ensured not to be blocked, because the total time for executing the whole rendering process (event scheduling, logic operation and page updating) in each frame frequency is ensured not to exceed 33 milliseconds. Therefore, compared with the prior art, the method and the device solve the problem of performance bottleneck caused by a large amount of communication between the Flash player and the JS page in the rendering process, so that rendered pictures have no pause in the card, and the user experience is good.
(2) In the invention, once the frame frequency event is monitored, the IO operation of the Flash player and the JS page is responded by using the IO data interface IOHandle which is appointed with the JS page and is used for receiving the transmission of the Flash player. Therefore, all IO operations can be limited to be processed in the response interface IOHandle of the FRAME frequency event ENTER _ FRAME, so that the number of IO communication is controlled in the response interface IOHandle, the program is prevented from having IO operations in other places, the number of IO operations can be increased, and unified IO operation management is facilitated.
(3) In the invention, when the data in the data cache pool is sent, the current data cache pool is emptied. Therefore, the data caching pool can timely cache new data sent by the server to avoid mixing with the data processed before, so that the new data can be sent to the JS page without mixing with the old data when the next frame frequency event is triggered (namely, the next frame frequency), repeated sending of the data is avoided, the accuracy is guaranteed, the efficiency is improved, and the communication performance is further improved.
Drawings
FIG. 1 is a flowchart of a method for efficient rendering communication between Flash and a JS page in an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a Flash and JS page efficient rendering communication device in the embodiment of the present invention;
FIG. 3 is a block diagram of a Flash and JS page efficient rendering communication system in an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the figures and the embodiments.
It is understood that the Flash player rendering is composed of frames, such as a 30-frame Flash animation, and 30 frames are rendered in 30.33 milliseconds and 30 frames are rendered in sequence like a slide one second, so that the user sees a 30-frame Flash animation. The 24 pictures are generally played in one second, and the user does not feel pause with eyes. Flash animation is smoother as more pictures are played in one second, and conversely, a user starts to feel like a pause in a card when the pictures are played in one second and is stronger when the pictures are played in one second and are fewer. Therefore, in order to solve the problem of pause in the card, the Flash player can ensure that enough pictures (preferably more than 24 pictures) are rendered every second while carrying out IO communication with the JS page, and the rendering time of each frame is less than 33 milliseconds on average in time.
The rendering process of the Flash frame can be divided into three processes according to the sequence: A. scheduling events, namely monitoring the bottom frame frequency events of the Flash player; B. performing logic operation, namely performing IO operation process on the Flash player and the JS page; C. and updating the page, namely rendering and updating the page. The page is guaranteed not to be stuck only if the three processes ABC are guaranteed to be executed for less than 33 milliseconds in total. And the time consumption of the IO operation of each Flash and JS page is about 1 millisecond, so in order to ensure no card, the IO operation of the Flash player and the JS page must be controlled to be operated only less than 10 times (slight floating can be achieved according to the difference of the browser, but usually, the number of the IO operations does not exceed 10 times) within the life cycle of 1 frame (namely, within one frame frequency).
Based on the design idea, referring to fig. 1, an embodiment of the present invention provides a method for efficient rendering communication between Flash and a JS page, where the method includes the following steps:
and step S1, creating and initializing a data cache pool, wherein the data cache pool is used for caching data received by the Flash player from the server, and the data cache pool comprises but is not limited to various animation pictures, animation information, data source information and the like required by the Flash player when the Flash player plays the animation.
Specifically, in actual operation, the data cache pool may be created by establishing an array of data cache pools. For example, this may be achieved by:
iodataist (iodataist ═ new Array ()), wherein iodataist is a data cache pool.
Step S2, establishing Socket (Socket) connection between the Flash player and the server; and setting an event monitor for monitoring whether the server has data to send.
Specifically, in one embodiment, step S2 specifically includes the following operations:
step S201, instantiating a Socket object in the Flash player, setting a server IP (Internet Protocol) to be connected and a server post parameter to be connected (post is a way of transmitting data to the server through an http post mechanism, and for the post way, the server side obtains submitted data by request.
Step S202, setting an event monitor for monitoring whether the server has data to send. In the step, event monitoring is set in advance, so that preparation is made for the Flash player to receive data sent by the server in time.
For example, in actual operation, a snoop event may be set to progress event. This event is triggered when the server sends a message to the Flash player. Specifically, the implementation code of steps S201, S202 may be as follows:
socket ()// instantiate the object of a Socket;
socket.set (IP, post)// setting a server IP needing to be connected and a server post parameter needing to be connected, and establishing Socket connection with the server;
SOCKET, addeventlestener (progressive event, SOCKET _ DATA, SOCKET _ DATAHANDLE)// setting is used for monitoring whether the server has an event monitoring from which DATA is sent; the monitoring event is progress event, SOCKET _ DATA, the response method is SOCKET _ DATAHANDLE, that is, step S3 hereinafter, and the response process is described in detail in step S3, which is not described herein again.
And step S3, receiving the data of the server and storing the data into the data cache pool once the data is monitored to be sent by the server. As described above by way of example, once a progress event, SOCKET _ DATA event, is snooped, in response to the SOCKET _ DATAHANDLE method, DATA from the server is received and stored in the DATA cache pool. Specifically, the implementation code of the SOCKET _ DATAHANDLE method may be: push (data).
S4, monitoring a frame frequency event at the bottom layer of the Flash player, and dividing data in a current data cache pool into N parts and sending the N parts to a JS page by using an IO data interface IOHandle which is appointed to the JS page and used for receiving the transmission of the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page.
Specifically, the implementation code for monitoring the FRAME frequency event underlying the Flash player may be stage. Wherein, ENTER _ FRAME represents a FRAME frequency event, and the response method is IOHandle. In addition, when the data in the current data cache pool is sent to the JS page (i.e., when IO operation is responded), an external interface call ("iohandle" is called as a system bottom layer method), where the datalist is a data set transmitted this time after the data cache pool is divided into N parts.
It can be understood that, in step S4, once the FRAME frequency event is monitored, the IO operation between the Flash player and the JS page is responded by using the IO data interface IOHandle appointed with the JS page for receiving the Flash player transmission, so that all IO operations can be limited to the response interface IOHandle of the FRAME frequency event ENTER _ FRAME for processing, and therefore, the number of IO communications is controlled in the response interface IOHandle, and programs are prevented from having IO operations in other places, which increases the number of IO operations, and facilitates uniform IO operation management.
In addition, in step S4, dividing the data in the current data cache pool into N parts and sending the N parts to the JS page instead of sending the N parts to the JS page at a time, takes into account that if the amount of the back data in the data cache pool IODATALIST is too large, the single IO operation data is very large, which increases page consumption and reduces the overall processing efficiency; the problem can be solved by sending the data in N times, and in order to ensure that the page is not stuck, in this embodiment, the value range of N is set to be not more than 10, preferably 10 times, that is, 1 millisecond sending time, so that the peak value of data communication can be reduced, and the picture can be ensured not to be stuck. Therefore, the performance bottleneck problem caused by a large amount of communication between the Flash player and the JS page in the rendering process is solved through the mode, rendered pictures have no pause feeling, and user experience is good.
Further, in practical applications, the number of data in the current data cache pool may be less than N. And if the situation occurs, one piece of data in the current data cache pool is sent to the JS page.
And step S5, when the data in the data cache pool is sent, emptying the current data cache pool. It can be understood that, after step S4, the current data cache pool is also emptied in step S5, so that the data cache pool can cache new data sent by the server in time and avoid mixing with the previously processed data, so that the new data is sent to the JS page without mixing with the old data when the next frame frequency event is triggered (i.e., in the next frame frequency), thereby avoiding repeated sending of data, ensuring accuracy and improving efficiency, and further improving communication performance.
Corresponding to the above method for efficient rendering communication of the Flash and the JS page, an embodiment of the present invention further provides a storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps of the method for efficient rendering communication of the Flash and the JS page in each embodiment may be implemented. The storage medium includes various media capable of storing program codes, such as a usb disk, a removable hard disk, a ROM (Read-Only Memory), a RAM (Random Access Memory), a magnetic disk, or an optical disk.
In addition, referring to fig. 2, corresponding to the above-mentioned method for efficiently rendering and communicating Flash and JS pages, an embodiment of the present invention further provides an apparatus for efficiently rendering and communicating Flash and JS pages, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor, when executing the computer program, can implement the steps of the method for efficiently rendering and communicating Flash and JS pages in each of the above-mentioned embodiments.
Referring to fig. 3, an embodiment of the present invention further provides an efficient rendering communication system for Flash and JS pages, where the system includes a data cache pool creation module, a server connection and monitoring setting module, a data cache module, and a rendering communication processing module. Wherein:
the data cache pool creation module is used for: and creating and initializing a data cache pool, wherein the data cache pool is used for caching data received by the Flash player from a server.
The server connecting and monitoring setting module is used for: establishing a Socket connection between the Flash player and the server, and setting an event monitor for monitoring whether the server has data sent. The specific implementation process comprises the following steps: instantiating a Socket object in the Flash player, setting a server IP (Internet protocol) required to be connected and a server post parameter required to be connected, and establishing Socket connection with a server; and then setting an event monitor for monitoring whether the server has data to send.
The data caching module is used for: once the server is monitored to send data, the data of the server is received and stored in a data cache pool;
the rendering communication processing module is used for: monitoring a frame frequency event at the bottom layer of the Flash player, dividing data in a current data cache pool into N parts and sending the N parts to a JS page for N times by using an IO data interface which is appointed with the JS page and is used for receiving the transmission of the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page. Further, if the number of the data in the current data cache pool is less than N, the rendering communication processing module sends one piece of data in the current data cache pool to the JS page. Furthermore, the rendering communication processing module divides the data in the current data cache pool into N parts and sends the N parts to the JS page, and then the current data cache pool is emptied.
It should be noted that: when the system provided by the embodiment implements efficient rendering communication between the Flash player and the JS page, the division of the functional modules is merely used for illustration, and in practical application, the function distribution can be completed by different functional modules according to needs, that is, the internal structure of the system is divided into different functional modules so as to complete all or part of the functions described above.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention.
Those not described in detail in this specification are within the skill of the art.

Claims (10)

1. A method for efficient rendering communication between Flash and a JS page is characterized by comprising the following operations:
establishing and initializing a data cache pool, wherein the data cache pool is used for caching data received by a Flash player from a server;
establishing Socket connection between the Flash player and the server, and setting an event monitor for monitoring whether the server has data sent;
once the server is monitored to send data, the data of the server is received and stored in a data cache pool;
monitoring a frame frequency event at the bottom layer of the Flash player, and dividing data in a current data cache pool into N parts and sending the N parts to a JS page for N times by using an IO data interface IOHandle which is appointed with the JS page and is used for receiving data transmitted by the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page, wherein the IOhandle is used for responding the IO operation of the Flash player and the JS page.
2. The method for efficient rendering communication between Flash and the JS page, as recited in claim 1, wherein: the specific operations of establishing a Socket connection between the Flash player and the server and setting a monitoring server for monitoring whether the server has an event monitoring function for sending data are as follows:
instantiating a Socket object in the Flash player, setting a server IP (Internet protocol) required to be connected and a server post parameter required to be connected, and establishing Socket connection with a server; and then setting an event monitor for monitoring whether the server has data to send.
3. The method for efficient rendering communication between Flash and the JS page, as recited in claim 1, wherein: and if the number of the data in the current data cache pool is less than N, one data in the current data cache pool is sent to the JS page.
4. The method for efficient rendering communication between Flash and the JS page, as recited in claim 1, wherein: and dividing the data in the current data cache pool into N parts, sending the N parts to the JS page for N times, and emptying the current data cache pool.
5. A storage medium having a computer program stored thereon, characterized in that: the computer program when executed by a processor implements the steps of the method of any of the preceding claims 1 to 4.
6. The utility model provides a Flash and JS page's high efficiency render communications facilities, includes memory, treater and stores in on the memory and the computer program who runs on the treater which characterized in that: the processor, when executing the computer program, realizes the steps of the method of any of the preceding claims 1 to 4.
7. The utility model provides a Flash and JS page's high efficiency communication system that renders which characterized in that: the system comprises a data cache pool creating module, a server connecting and monitoring setting module, a data cache module and a rendering communication processing module;
the data cache pool creation module is configured to: establishing and initializing a data cache pool, wherein the data cache pool is used for caching data received by a Flash player from a server;
the server connecting and monitoring setting module is used for: establishing Socket connection between the Flash player and the server, and setting an event monitor for monitoring whether the server has data sent;
the data caching module is used for: once the server is monitored to send data, the data of the server is received and stored in a data cache pool;
the rendering communication processing module is used for: monitoring a frame frequency event at the bottom layer of the Flash player, and dividing data in a current data cache pool into N parts and sending the N parts to a JS page for N times by using an IO data interface IOhandle which is appointed with the JS page and is used for receiving data transmitted by the Flash player once the frame frequency event is monitored, wherein N is a positive integer which is more than 1 and less than or equal to 10; and after the JS page receives the data sent by the Flash player, rendering the bottom layer according to the data to update the current JS page, wherein the IOhandle is used for responding the IO operation of the Flash player and the JS page.
8. The Flash and JS page efficient rendering communication system of claim 7, wherein: the server connection and monitoring setting module establishes Socket connection between the Flash player and the server, and sets a specific operation for monitoring whether the server has event monitoring of data transmission as follows:
instantiating a Socket object in the Flash player, setting a server IP (Internet protocol) required to be connected and a server post parameter required to be connected, and establishing Socket connection with a server; and then setting an event monitor for monitoring whether the server has data to send.
9. The Flash and JS page efficient rendering communication system of claim 7, wherein: and if the number of the data in the current data cache pool is less than N, the rendering communication processing module sends one piece of data in the current data cache pool to the JS page.
10. The Flash and JS page efficient rendering communication system of claim 7, wherein: and the rendering communication processing module divides the data in the current data cache pool into N parts and sends the N parts to the JS page, and then the current data cache pool is emptied.
CN201710932695.0A 2017-10-10 2017-10-10 Flash and JS page efficient rendering communication method, storage medium, device and system Active CN107743266B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710932695.0A CN107743266B (en) 2017-10-10 2017-10-10 Flash and JS page efficient rendering communication method, storage medium, device and system
PCT/CN2017/117382 WO2019071830A1 (en) 2017-10-10 2017-12-20 Flash and js page efficient rendering communication method, storage medium, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710932695.0A CN107743266B (en) 2017-10-10 2017-10-10 Flash and JS page efficient rendering communication method, storage medium, device and system

Publications (2)

Publication Number Publication Date
CN107743266A CN107743266A (en) 2018-02-27
CN107743266B true CN107743266B (en) 2020-01-03

Family

ID=61237053

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710932695.0A Active CN107743266B (en) 2017-10-10 2017-10-10 Flash and JS page efficient rendering communication method, storage medium, device and system

Country Status (2)

Country Link
CN (1) CN107743266B (en)
WO (1) WO2019071830A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109831701B (en) * 2019-01-28 2021-12-21 四川长虹电器股份有限公司 Digital television equipment browser and method for expanding cross-page system event

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478669A (en) * 2008-08-29 2009-07-08 百视通网络电视技术发展有限责任公司 Media playing control method based on browser on IPTV system
WO2014169860A1 (en) * 2013-09-26 2014-10-23 中兴通讯股份有限公司 Data transmission method and device
CN105898520A (en) * 2016-04-07 2016-08-24 合网络技术(北京)有限公司 Video frame interception method and device
CN106131142A (en) * 2016-06-27 2016-11-16 乐视控股(北京)有限公司 multimedia data storage method and device
WO2016197865A1 (en) * 2015-06-11 2016-12-15 阿里巴巴集团控股有限公司 Data transmission method and apparatus, and smart television system
CN106330878A (en) * 2016-08-18 2017-01-11 乐视控股(北京)有限公司 Method and device for managing video streaming resolution

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7269784B1 (en) * 2001-01-22 2007-09-11 Kasriel Stephane Server-originated differential caching
CN105677688B (en) * 2014-11-21 2019-07-16 博雅网络游戏开发(深圳)有限公司 Page data loading method and system
CN106156148B (en) * 2015-04-14 2020-08-21 腾讯科技(深圳)有限公司 Page rendering method and device and terminal equipment
CN106991096B (en) * 2016-01-21 2021-03-02 阿里巴巴集团控股有限公司 Dynamic page rendering method and device
CN105824874A (en) * 2016-02-01 2016-08-03 乐视移动智能信息技术(北京)有限公司 Mobile terminal as well as web page rendering method and device thereof

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478669A (en) * 2008-08-29 2009-07-08 百视通网络电视技术发展有限责任公司 Media playing control method based on browser on IPTV system
WO2014169860A1 (en) * 2013-09-26 2014-10-23 中兴通讯股份有限公司 Data transmission method and device
WO2016197865A1 (en) * 2015-06-11 2016-12-15 阿里巴巴集团控股有限公司 Data transmission method and apparatus, and smart television system
CN105898520A (en) * 2016-04-07 2016-08-24 合网络技术(北京)有限公司 Video frame interception method and device
CN106131142A (en) * 2016-06-27 2016-11-16 乐视控股(北京)有限公司 multimedia data storage method and device
CN106330878A (en) * 2016-08-18 2017-01-11 乐视控股(北京)有限公司 Method and device for managing video streaming resolution

Also Published As

Publication number Publication date
WO2019071830A1 (en) 2019-04-18
CN107743266A (en) 2018-02-27

Similar Documents

Publication Publication Date Title
CN106850589B (en) Method for managing and controlling operation of cloud computing terminal and cloud server
CN102761564B (en) Graphic sharing method, system and terminal
CA2557111A1 (en) System and method for building mixed mode execution environment for component applications
CN103650458A (en) Transmission method, device and system of media streams
JP2004527028A5 (en)
CN111182019B (en) Cross-platform communication method and device and electronic equipment
CN112260853B (en) Disaster recovery switching method and device, storage medium and electronic equipment
CN111625353B (en) Virtual resource distribution processing method, device, server and storage medium
WO2021159831A1 (en) Programming platform user code running method, platform, node, device and medium
CN107743266B (en) Flash and JS page efficient rendering communication method, storage medium, device and system
KR20070024183A (en) Method for controlling data transmission and network apparatus transmitting data by using the same
KR20170107667A (en) Method and system for transmitting remote screen
US11539919B1 (en) Dynamic cloud video composition
CN112689012A (en) Cross-network proxy communication method and device
CN112073488A (en) Method and device for processing request
CN111767558A (en) Data access monitoring method, device and system
CN111190731A (en) Cluster task scheduling system based on weight
CN116233209A (en) Remote management scheduling method for GPU cloud rendering service
CN115364477A (en) Cloud game control method and device, electronic equipment and storage medium
CN105357243B (en) A kind of method and apparatus with internet of things equipment remote interaction
CN113891123A (en) Method, device and system for pushing virtual space information
CN108377243B (en) Live streaming transmission method and device
CN113075993B (en) Video display method, device, storage medium and electronic equipment
CN109062620A (en) Android frame animation executes method, apparatus, terminal and readable medium
CN112486700B (en) Communication method, device and storage medium

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
GR01 Patent grant
GR01 Patent grant