CN110688233B - Client ipc communication method, storage medium, equipment and system based on rxjs - Google Patents
Client ipc communication method, storage medium, equipment and system based on rxjs Download PDFInfo
- Publication number
- CN110688233B CN110688233B CN201810732401.4A CN201810732401A CN110688233B CN 110688233 B CN110688233 B CN 110688233B CN 201810732401 A CN201810732401 A CN 201810732401A CN 110688233 B CN110688233 B CN 110688233B
- Authority
- CN
- China
- Prior art keywords
- client
- data
- callback function
- data stream
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Abstract
The invention discloses a client ipc communication method, a storage medium, equipment and a system based on rxjs, relating to the field of mobile terminal data communication, wherein the method comprises the steps of establishing a QT inner core and an anonymous pipeline for communication between a client process and a web engine process in a client; configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list; creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data; and binding the created rx data stream with the ipc channel signal to form a correspondence between the rx data stream and the signal data received by the client. The invention can effectively avoid the problem of data loss between the client and the server.
Description
Technical Field
The invention relates to the field of mobile terminal data communication, in particular to a client ipc communication method, a storage medium, equipment and a system based on rxjs.
Background
With the rapid development of intelligent mobile electronic devices, mobile-end application program functions are becoming more abundant, and more developers are added to the development of mobile-end application programs.
The mobile terminal application program that corresponds general use at present, communication between client and the server still is based on web socket's connected mode, and in some specific cases, operating system's firewall can intercept web socket's connected communication, like the live broadcast client, if operating system's firewall intercepts the web socket connected communication between barrage server and the live broadcast client, leads to the unable normal display barrage of live broadcast client, and then influences user's live broadcast viewing experience.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a client ipc communication method based on rxjs, which can effectively avoid the problem of data loss between a client and a server.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows:
creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list;
creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data;
and binding the created rx data stream with the ipc channel signal to form a correspondence between the rx data stream and the signal data received by the client.
On the basis of the technical scheme, the rx data stream is used for receiving data in the ipc channel signal bound with the rx data stream and caching the received data.
On the basis of the technical scheme, after the rx data stream receives the data, the corresponding subscriber responds to the data and processes the data.
On the basis of the technical proposal, the device comprises a shell,
a callback function stack is also established in the client;
when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, assembles the callback function and the random key and then puts the callback function and the random key into a callback function stack;
and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
On the basis of the technical scheme, a timing task is set for the callback function stack, and executed callback functions in the callback function stack are periodically cleaned within a timing period of the timing task.
On the basis of the technical scheme, when developing and debugging the client:
creating a node transit service locally;
forwarding interface data of the development environment to a node transfer service of a client;
the node transfer service encrypts and authenticates interface data and then sends the interface data to the server.
On the basis of the technical scheme, the node transfer service encrypts and authenticates interface data and then sends the interface data to the server, and the specific steps are as follows: and starting the web service by using a node express frame module in the node transit service, encrypting and authenticating the interface data, and then sending the processed interface data to the server.
The present invention also provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list;
creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data;
and binding the created rx data stream with the ipc channel signal to form a correspondence between the rx data stream and the signal data received by the client.
The present invention also provides an electronic device comprising:
the client side comprises a first creating unit, a second creating unit and a third creating unit, wherein the first creating unit is used for creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client side;
the configuration unit is used for configuring a white list for communication between the client and the server in the client and adding signal data required by web view page interaction to the white list;
a second creating unit, configured to create an rx data stream having the same name as the client-side received signal data, where the rx data stream is used to receive specified data and subscribe to the data;
and the binding unit is used for binding the created rx data stream and the ipc channel signal to form the correspondence of the relationship between the rx data stream and the signal data received by the client.
The invention also provides a client ipc communication system based on rxjs, which comprises:
the client comprises a first creation module, a first creation module and a second creation module, wherein the first creation module is used for creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
the configuration module is used for configuring a white list for communication between the client and the server in the client and adding signal data required by web view page interaction to the white list;
a second creating module, configured to create an rx data stream having the same name as the client-side received signal data, where the rx data stream is used to receive specified data and subscribe to the data;
and the binding module is used for binding the created rx data stream with the ipc channel signal to form the correspondence of the relationship between the rx data stream and the signal data received by the client.
Compared with the prior art, the invention has the advantages that: by establishing the QT kernel in the client, the server and the client communicate based on the ipc, the problem of data loss between the client and the server in the existing web socket connection communication mode is effectively solved, the created rx data stream is bound with an ipc channel signal, and a subscriber corresponds to the rx data stream, so that after the client receives the data, the corresponding subscriber can immediately process the data, and the data processing efficiency is improved.
Drawings
Fig. 1 is a flowchart of a rxjs-based client ipc communication method in an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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.
Referring to fig. 1, an embodiment of the present invention provides a rxjs-based client ipc communication method, which is used for performing communication between a client and a server, for example, between a mobile live broadcast client and a barrage server, and ensuring integrity of a client interface data stream. rxjs is a JavaScript version of the realvex programming philosophy, available from microsoft, which is a programming for asynchronous data streams, for packaging data, such as HTTP requests, DOM events, or common data, in a streamed form. ipc (Inter-Process Communication) is Inter-Process Communication. The client ipc communication method based on rxjs in the embodiment of the invention specifically comprises the following steps:
s1: and creating a QT kernel and an anonymous pipeline for communication between the client process and the web engine process in the client. QT was a cross-platform C + + graphical user interface application development framework developed by QT Company in 1991. The client side can support the ipc channel only by containing the QT kernel, the QT kernel of the latest version is preferably established in the client side, compatibility is guaranteed, if the client side does not contain the QT kernel, the communication mode of the ipc cannot be used, and only the previous websocket scheme can be used. An anonymous pipe is created by the host process of the client.
S2: the method comprises the steps that a white list for communication between a client and a server is configured in the client, signal data required by webview page interaction is added to the white list, namely the signal data required by the webview page is added to the white list in a white list creating mode, so that the client can only receive the data required by the webview page, other page data are rejected, the relative uniformity of the client and the webview page is kept, and the equipment performance overhead caused by unnecessary signal processing is reduced.
S3: and creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data. The client receives multiple signal data, such as response data, bullet screen data, authentication data and the like, the created rx data stream is the same name as the received signal data, if the rx data stream is created, the rx data stream is used for receiving the response data sent to the client by the server, and meanwhile, the rx data stream subscribes the data, so that certain data can only be received by a specific subscriber, and if a subscriber subscribes the response data corresponding to the rx data stream, the client processes the response data corresponding to the subscriber after receiving the response data.
And the rx data stream is used for receiving the data in the ipc channel signal bound with the rx data stream and buffering the received data. When rx data stream receives data, the corresponding subscriber responds to and processes the data, the subscriber immediately processes the newly arrived data after receiving the newly arrived data, and simultaneously, the subscriber immediately processes the corresponding old data after detecting the corresponding old data, thereby perfectly solving the timing sequence problem possibly caused by asynchronous communication, and the subscriber can process the data at the designated position, thereby increasing the code superiority and maintainability. The QT framework creates communication channel data into a series of self-defined signals, introduces rxjs into a front-end webview page, creates an rx data stream for each signal, and receives and buffers the data.
The rxjs data streams correspond to each ipc channel signal, a certain amount of historical data records are reserved in the corresponding rx data streams, the rx data streams can be called by subscribing at any required time, and all channel monitoring functions do not need to be declared before initialization. The contact degree between the rxjs asynchronous thought and the existing act framework is higher, and the subscribers are integrated into the acts, so that the acts can become observable behaviors, and the view response is facilitated.
S4: and binding the created rx data stream with the ipc channel signal to form a correspondence between the rx data stream and the signal data received by the client. The data sent to the client by the server are various, different data correspond to different ipc channel signals, the created rx data stream also corresponds to different data, so that the rx data stream and the ipc channel signals can establish a corresponding relation based on the same data, and meanwhile, a subscriber can subscribe the data through the rx data stream, so that the ipc channel signals, the rx data stream and the subscriber can establish a corresponding relation, and the corresponding subscriber can respond and process at the first time after the client receives certain signal data.
According to the client-side ipc communication method based on rxjs, the existing QT + websocket communication interaction strategy is abandoned in a communication layer, an ipc-type channel communication mode is carried out by using a webChanelTransport object, and an anonymous pipeline is adopted at the bottom layer for communication; the client data can reuse a data interface API inside a dll related to qml created by an original QT framework, and the upper layer of the client has small change content in the development process.
In the prior art, a webview page of a client is increased rapidly, and a series of security problems are caused, for example, to ensure the security of data, an interface of the client needs to be added with interface authentication, an encryption key required by the authentication cannot be stored in a webpage based on a security policy, the authentication interface needs to be forwarded by the client, communication data of an original ws protocol may be intercepted by a packet and then forwarded by a middleware, and a lawless person pretends to pass through a server for verification to obtain server data, so that the server data is leaked. In the embodiment of the invention, aiming at the authentication process between a client and a server, a callback function stack is established in the client, when the client interacts with the server each time, the server establishes a specified callback function and a random key and sends the created callback function and the random key to the client, and an rx data stream of the client receives the callback function and the random key and is put into the callback function stack after being assembled; the method comprises the steps that when authentication interaction is carried out between a subscription client and a server, the server responds rx data flow of the client, a callback function received by the response rx data flow is obtained, whether the callback function is contained in a callback function stack or not is judged, if yes, the callback function is executed, namely, a page sends a conventional request (the device carries out assembling and data encryption authentication, the server receives parameters after authentication and returns a request result), the response is received, the interruption behaviors of the authentication and the data flow in the middle process are not sensed, and the conventional development habit is matched. An independent key is generated for each request, the responded key is matched with the request, invalid data are directly discarded, and unnecessary performance overhead caused by subsequent multi-page application can be effectively avoided. The method comprises the following steps that interaction between a client and a server is realized, a token local to the client is integrated into a request parameter when each request of the client is carried out, and the token is integrated by the client under a development environment.
Furthermore, a timing task is set for the callback function stack, executed callback functions in the callback function stack are periodically cleaned in the timing period of the timing task, namely, the callback function stack can be regularly inquired through timing service, callback functions which are invalid, exceed the set time or are executed are searched, then the searched callback functions are cleaned, and the situation that the client runs short due to the fact that the memory of the callback function stack is excessively occupied is avoided.
Because the client QT kernel does not support the Source map, and the new communication mode has no open remote connection port, the debugging can only be carried out in the client, and the Source code in the development process cannot be tracked, the Source Maps can restore the compressed file to the original position of the Source file in the client integrated development mode. For the development mode of the client: creating node transit service locally, wherein the local refers to the environment where development is located; the interface data of the development environment is forwarded to a node transit service on a node transit service of a client to encrypt and authenticate the interface data and then send the encrypted and authenticated interface data to a server, the authentication method used here can be the authentication method or a conventional authentication method (such as token authentication and the like), the encryption here can be realized by using a conventional encryption algorithm (such as an asymmetric encryption algorithm and the like), the service is configured with a quick-start batch processing file, a script required by the service is integrated in the device, the compiling process is automatically ignored and is not exposed in a formal environment, the security of an encryption key is ensured, meanwhile, the node transit service returns result data, the interface environment of the client is simulated, and the development mode requirements on the client are met. The node in the embodiment of the invention refers to node.
The method comprises the following steps of encrypting and authenticating interface data by a node transfer service and then sending the interface data to a server, wherein the specific steps are as follows: the method comprises the steps of starting Web services by using a node Express framework module in a node transit service, encrypting and authenticating interface data, then sending the processed interface data to a server, establishing an Express framework on an Http module built in node js, and repackaging the Http module, thereby realizing the function of processing an actual Web request. It supports a variety of front-end templates, such as Jade, EJS, etc. For node transit service, a node express module is used for starting web service, after receiving an interface request, operations such as encryption, authentication and the like are carried out, and then a request module is used for forwarding to a server side. The request module is an HTTP client in the node, and can be used for realizing the switching of TTP response flow, simulating Form submission, supporting HTTP authentication, OAuth login, self-defining request header and the like. Aiming at the login token in the development mode in the client, a localStorage cache token is utilized, the client login state is absent in the development environment, the manual change can be realized, and the automatic transmission is realized within the validity period of the token. And after receiving the response data, the client takes out the independent key created in the request, assembles the key and the response data, pushes the key and the response data into rx data stream corresponding to authentication, and keeps the data stream direction consistent with the formal environment.
According to the client-side ipc communication method based on rxjs, the server and the client-side communicate based on the ipc by establishing the QT kernel in the client-side, the problem of data loss between the client-side and the server in the existing web socket connection communication mode is effectively solved, the created rx data stream is bound with the ipc channel signal, and a subscriber corresponds to the rx data stream, so that the client-side can immediately process the data after receiving the data, and the data processing efficiency is improved.
An embodiment of the present invention further provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the following steps:
creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list;
creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data;
and binding the created rx data stream with the ipc channel signal to form a correspondence between the rx data stream and the signal data received by the client.
The rx data stream is used for receiving data in the ipc channel signal bound with the rx data stream, caching the received data, and after the rx data stream receives the data, the corresponding subscriber responds to and processes the data. Furthermore, a callback function stack is also established in the client; when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, is assembled and then is placed in a callback function stack; and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
Referring to fig. 2, an embodiment of the present invention further provides an electronic device, which includes a first creating unit 501, a configuring unit 502, a second creating unit 503, and a binding unit 504.
The first creating unit 501 is used for creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client; the configuration unit 502 is configured to configure a white list for communication between a client and a server in the client, and add signal data required for webview page interaction to the white list; the second creating unit 503 is configured to create an rx data stream having the same name as the client-side received signal data, where the rx data stream is used to receive specified data and subscribe data; the binding unit 504 is configured to bind the created rx data stream with the ipc channel signal, so as to form a correspondence between the rx data stream and the signal data received by the client. And the rx data stream is used for receiving the data in the ipc channel signal bound with the rx data stream, caching the received data, and after the rx data stream receives the data, the corresponding subscriber responds to and processes the data.
The embodiment of the invention also provides a client-side ipc communication system based on rxjs, which comprises a first creation module, a configuration module, a second creation module and a binding module.
The first creating module is used for creating a QT kernel in a client and an anonymous pipeline for communication between a client process and a web engine process; the configuration module is used for configuring a white list for communication between the client and the server in the client and adding signal data required by web view page interaction to the white list; the second establishing module is used for establishing rx data streams with the same name as the signal data received by the client, and the rx data streams are used for receiving specified data and subscribing the data; and the binding module is used for binding the created rx data stream with the ipc channel signal to form the correspondence of the relationship between the rx data stream and the signal data received by the client.
The rx data stream created by the second creation module is used for receiving the data in the ipc channel signal bound with the rx data stream and buffering the received data. And when the rx data stream receives the data, the corresponding subscriber responds to the data and processes the data.
According to the client-side ipc communication system based on rxjs, the server and the client-side communicate based on the iPC by establishing the QT kernel in the client-side, the problem of data loss between the client-side and the server in the existing web socket connection communication mode is effectively solved, the created rx data stream is bound with the ipc channel signal, and a subscriber corresponds to the rx data stream, so that the client-side can immediately process the data after receiving the data, and the data processing efficiency is improved.
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 (9)
1. A client ipc communication method based on rxjs is characterized by comprising the following steps:
creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list;
creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data;
binding the created rx data stream with an ipc channel signal to form correspondence between the rx data stream and signal data received by a client;
a callback function stack is also established in the client;
when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, assembles the callback function and the random key and then puts the callback function and the random key into a callback function stack;
and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
2. The rxjs-based client ipc communication method of claim 1, wherein: and the rx data stream is used for receiving the data in the ipc channel signal bound with the rx data stream and buffering the received data.
3. The rxjs-based client ipc communication method of claim 2, wherein: and when the rx data stream receives the data, the corresponding subscriber responds to the data and processes the data.
4. The rxjs-based client ipc communication method of claim 1, wherein: setting a timing task for the callback function stack, and periodically cleaning the executed callback functions in the callback function stack in the timing period of the timing task.
5. The rxjs-based client ipc communication method of claim 1, wherein when developing and debugging the client:
creating a node transit service locally;
forwarding interface data of the development environment to a node transfer service of a client;
the node transfer service encrypts and authenticates interface data and then sends the interface data to the server.
6. The rxjs-based client ipc communication method of claim 5, wherein: the node transfer service encrypts and authenticates interface data and then sends the interface data to a server, and the method specifically comprises the following steps: and starting the web service by using a node express frame module in the node transit service, encrypting and authenticating the interface data, and then sending the processed interface data to the server.
7. A storage medium having a computer program stored thereon, the computer program, when executed by a processor, performing the steps of:
creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
configuring a white list for communication between a client and a server in the client, and adding signal data required by web view page interaction to the white list;
creating an rx data stream with the same name as the client-side received signal data, wherein the rx data stream is used for receiving specified data and subscribing the data;
binding the created rx data stream with an ipc channel signal to form a correspondence between the rx data stream and signal data received by a client;
a callback function stack is also established in the client;
when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, assembles the callback function and the random key and then puts the callback function and the random key into a callback function stack;
and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
8. An electronic device, comprising:
the client side comprises a first creating unit, a second creating unit and a third creating unit, wherein the first creating unit is used for creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client side;
the configuration unit is used for configuring a white list for communication between the client and the server in the client and adding signal data required by web view page interaction to the white list;
a second creating unit, configured to create an rx data stream having the same name as the client-side received signal data, where the rx data stream is used to receive specified data and subscribe to the data;
the binding unit is used for binding the created rx data stream with the ipc channel signal to form the correspondence of the relationship between the rx data stream and the signal data received by the client;
a callback function stack is also established in the client;
when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, assembles the callback function and the random key and then puts the callback function and the random key into a callback function stack;
and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
9. An rxjs-based client ipc communication system, comprising:
the client comprises a first creation module, a first creation module and a second creation module, wherein the first creation module is used for creating a QT kernel and an anonymous pipeline for communication between a client process and a web engine process in a client;
the configuration module is used for configuring a white list for communication between the client and the server in the client and adding signal data required by web view page interaction to the white list;
a second creating module, configured to create an rx data stream having the same name as the client-side received signal data, where the rx data stream is used to receive specified data and subscribe to the data;
the binding module is used for binding the created rx data stream with the ipc channel signal to form the correspondence of the relationship between the rx data stream and the signal data received by the client;
a callback function stack is also established in the client;
when the client interacts with the server every time, the server creates a specified callback function and a random key and sends the created callback function and the created random key to the client, and the rx data stream of the client receives the callback function and the random key, assembles the callback function and the random key and then puts the callback function and the random key into a callback function stack;
and when the authentication interaction between the subscription client and the server is carried out, the server acquires a callback function received by the response rx data stream to the response rx data stream of the client, judges whether the callback function stack contains the callback function, and executes the callback function if the callback function stack contains the callback function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810732401.4A CN110688233B (en) | 2018-07-05 | 2018-07-05 | Client ipc communication method, storage medium, equipment and system based on rxjs |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810732401.4A CN110688233B (en) | 2018-07-05 | 2018-07-05 | Client ipc communication method, storage medium, equipment and system based on rxjs |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110688233A CN110688233A (en) | 2020-01-14 |
| CN110688233B true CN110688233B (en) | 2022-05-10 |
Family
ID=69106847
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810732401.4A Active CN110688233B (en) | 2018-07-05 | 2018-07-05 | Client ipc communication method, storage medium, equipment and system based on rxjs |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110688233B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4064053A1 (en) | 2021-03-26 | 2022-09-28 | Aptiv Technologies Limited | Managing inter-service communication |
| CN116820431B (en) * | 2023-08-30 | 2023-11-14 | 山东威尔数据股份有限公司 | Embedded application development and operation method with full function node. Js |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981841A (en) * | 2011-11-08 | 2013-03-20 | 微软公司 | External serialization and deserialization |
| CN103679368A (en) * | 2013-12-13 | 2014-03-26 | 清华大学 | Wafer CMP processing information management system |
| CN106657344A (en) * | 2016-12-27 | 2017-05-10 | 四川中电启明星信息技术有限公司 | Terminal browser operation system and communication method of the same |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571934A (en) * | 2011-12-22 | 2012-07-11 | 深圳华强电子交易网络有限公司 | WEB page data binding method |
| US10540266B2 (en) * | 2016-09-27 | 2020-01-21 | Profilence Oy | Method and system for testing software based system |
| CN106713360B (en) * | 2017-02-15 | 2020-05-08 | 上海市共进通信技术有限公司 | Method for realizing web encryption access and information encryption storage based on gateway equipment |
-
2018
- 2018-07-05 CN CN201810732401.4A patent/CN110688233B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981841A (en) * | 2011-11-08 | 2013-03-20 | 微软公司 | External serialization and deserialization |
| CN103679368A (en) * | 2013-12-13 | 2014-03-26 | 清华大学 | Wafer CMP processing information management system |
| CN106657344A (en) * | 2016-12-27 | 2017-05-10 | 四川中电启明星信息技术有限公司 | Terminal browser operation system and communication method of the same |
Non-Patent Citations (7)
| Title |
|---|
| 2分钟！使用express快速创建一个服务器;否子戈;《https://segmentfault.com/a/1190000008202132》;20170123;1-2 * |
| Angular HttpClient使用RxJS Observable例子;leftso;《https://www.leftso.com/blog/453.html》;20180704;1-7 * |
| JavaScript in mobile applications: React native vs ionic vs NativeScript vs native development;Hugo Brito等;《2018 13th Iberian Conference on Information Systems and Technologies (CISTI)》;20180628 * |
| RxJS之ReplaySubject;箭雨;《https://zhuanlan.zhihu.com/p/28808860》;20170826;1-2 * |
| Web单页技术在桌面程序开发中的应用;徐玖超等;《计算机产品与流通》;20180215(第2期);38 * |
| 使用angular的HttpClient搭配rxjs;Yitim;《https://www.cnblogs.com/yitim/p/7458576.html》;20170831;1-4 * |
| 实现QT与HTML页面通信;liuyez123;《https://blog.csdn.net/liuyez123/article/details/50509788?locationNum=10&fps=1》;20160113;1-9 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110688233A (en) | 2020-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11799985B2 (en) | System and method for improving internet communication by using intermediate nodes | |
| US9413830B2 (en) | Application streaming service | |
| US11425052B2 (en) | Discovery and adjustment of path maximum transmission unit | |
| US10034057B2 (en) | Message processing method, device, gateway, STB and IPTV | |
| US10645172B1 (en) | Socket tunneling connections in a service provider environment | |
| CN109413219B (en) | Domain name resolution method and device, server and storage medium | |
| CN110688233B (en) | Client ipc communication method, storage medium, equipment and system based on rxjs | |
| CN107332894B (en) | Live broadcast method, device and system, server and storage medium | |
| CN111212117A (en) | Remote interaction method and device | |
| US20230418583A1 (en) | Containerized, decentralized, and distributed web applications with end-to-end encryption | |
| JP2005501354A (en) | Method and system for providing web services with multiple web domains via a single IP address | |
| CN111327680B (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| CN115604862B (en) | Video streaming transmission method and system | |
| EP3276914A1 (en) | Data sharing method and device for virtual desktop | |
| JP6351000B2 (en) | Broadcast reception system and broadcast communication cooperation system | |
| CN115189897A (en) | Access processing method and device for zero trust network, electronic equipment and storage medium | |
| JP2003330886A (en) | Network processing device | |
| WO2016188315A1 (en) | Method for pushing multimedia information and terminal | |
| CN109600379B (en) | Noise reduction method and device for HTTPS redirection | |
| CN111240868B (en) | Instance processing and calling method, device, system and storage medium | |
| KR20180046135A (en) | Cloud settopbox apparatus | |
| CN107454580B (en) | Method and system for realizing directional guidance of application program flow and mobile terminal | |
| CN116156020A (en) | Data processing method, device and readable storage medium | |
| CN114710711A (en) | Equipment upgrading method and device, electronic equipment and storage medium | |
| CN112422566A (en) | Remote call processing method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |