CN112214333A - Webpage and local application communication protocol based on HTTP (hyper text transport protocol) and application - Google Patents
Webpage and local application communication protocol based on HTTP (hyper text transport protocol) and application Download PDFInfo
- Publication number
- CN112214333A CN112214333A CN202011008148.1A CN202011008148A CN112214333A CN 112214333 A CN112214333 A CN 112214333A CN 202011008148 A CN202011008148 A CN 202011008148A CN 112214333 A CN112214333 A CN 112214333A
- Authority
- CN
- China
- Prior art keywords
- data
- communication
- protocol
- application
- http
- 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
- 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/541—Interprogram communication via adapters, e.g. between incompatible applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/03—Protocol definition or specification
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
The invention provides a communication protocol and application of a webpage and a local application based on an HTTP (hyper text transport protocol). The communication protocol and application of the webpage and the local application based on the HTTP protocol comprise: the method comprises the following steps of defining a communication protocol, a webpage end communication packet and a client end communication packet; the communication protocol definition comprises a communication mode definition and a communication protocol format; the communication protocol adopted by the communication mode definition is based on an HTTP protocol. The webpage based on the HTTP protocol, the local application communication protocol and the application provided by the invention have the advantages that the communication is realized by using the universal HTTP protocol, the cross-language, the cross-application and the direct local communication can be realized, the communication among different applications is directly carried out without the transfer of a server, the extensible localization capability is provided for the webpage, the limitation of a browser is avoided by a technical means, the localization capability is added to the existing webpage at any time, the original functions are not required to be modified greatly, the technical route is not required to be changed, the framework is not required to be adjusted, and only a service interface is required to be added.
Description
Technical Field
The invention relates to the field of computer software, in particular to a communication protocol and application of a webpage and a local application based on an HTTP (hyper text transport protocol).
Background
There are many local applications on the market today, including various program operating systems, various development languages, off-the-shelf or self-developed, due to the influence of technical capability, framework technical limit, development time and the like, although part of software supports extended development, the whole experience is not good particularly on UI interaction, moreover, because the technology difference is large, the development cost is very high, and in addition, the current newer software platform depends on a browser based on the BS framework, but the access to local resources is limited by the restriction of a browser, some local applications either need to build a frame again for development, so that the investment cost is huge, or the development of a mixed mode is used, so that the local applications cannot be well integrated with some mature local applications in the prior art, and in addition, among different local applications, if the communication mode is not defined at first, good data communication cannot be carried out, and higher development cost is required to be invested in communication at a later stage if the communication is required.
At present, no technology for directly communicating a webpage with a local application is realized, the webpage and the local application are all transferred through a server or are in a mixed mode through a self-defined APP or browser mode, the architecture is complex, and a program or a part of an earlier program does not have a network access function and is difficult to modify.
Therefore, it is necessary to provide a communication protocol and application for web pages and local applications based on HTTP protocol to solve the above technical problems.
Disclosure of Invention
The invention provides a communication protocol and application of a webpage and a local application based on an HTTP protocol, and solves the technical problem that no webpage and local application are in direct communication.
In order to solve the above technical problems, the communication protocol and application between the web page and the local application based on the HTTP protocol provided by the present invention includes: the method comprises the following steps of defining a communication protocol, a webpage end communication packet and a client end communication packet; the communication protocol definition comprises a communication mode definition and a communication protocol format; the communication protocol adopted by the communication mode definition is based on an HTTP protocol, an HTTP service module is integrated by local application, the HTTP service is started, in order to ensure that the safe HTTP service only monitors 127.0.0.1 local IP and only allows local calling, a service port is 36666 by default and can be arbitrarily designated as a legal port, the safe HTTP service is started in sequence, if the safe HTTP service is started successfully, the safe HTTP service is fixed as a current port, if the safe HTTP service is started successfully, a standby port is tried, and if all port attempts fail, the safe HTTP service is stopped; the communication protocol format adopts a communication format that all communication is based on an HTTP standard, only GET requests are used for improving compatibility, all requests are sent by a webpage end, and the protocol defines four communication API interfaces including a health check interface, a command execution interface, a client push interface and an exit program;
the webpage end communication packet comprises a webpage end communication packet function;
the client communication packet includes a client communication packet function.
Preferably, the service ports also include 36667 and 36668, 36667 and 36668 as a default for standby, and the local HTTP service needs to turn on CORS cross-domain access support.
Preferably, the health check interface:
URL：/health；
parameters are as follows:
t: the time stamp is millisecond number and is automatically generated during calling;
interface types are as follows: and (4) automatic.
Preferably, the health check interface is operable to: polling is carried out all the time once the webpage communication is started, whether the state of a local client program is normal is checked, polling is carried out once per second by default, and the timeout time is 1 second;
and returning a value:
{
"status": true,// fixed return;
"data": 0// returning a number greater than 0 when there is data to push to the front end, otherwise returning 0;
}。
preferably, the command execution interface:
URL：/exec；
parameters are as follows:
cmd: the execution command ID is used for distinguishing which kind of service is specifically executed, and different IDs are defined to realize that the same interface executes different services when the command ID is actually applied;
t: the time stamp is millisecond number and is automatically generated during calling;
bizData: converting data sent by the data into text content after JSON character strings;
uuid: the unique id of the command sent at this time is automatically generated and used for tracking the asynchronous return value and distinguishing when the command is split;
i: if the split is not needed, the transmission is not carried out, if the split is needed, the current packet is represented as the number of packets, and the sequence number is started from 0;
reduce: if the split is not needed, the transmission is not carried out, and if the split is needed, the number of the packets which are split together is represented;
interface types are as follows: and (4) manually operating.
Preferably, the command of the command execution interface is initiated by a browser end, and a command is sent to a local client program, because the maximum length of the URL of the GET request is about 8000 characters, when the length of the sent data is too long, the data needs to be split, for the split data, uuid in each request is the same value, reduce is the number of split pieces, and i is the current i-th segment; the back end receives incomplete data and can not carry out analysis operation, and logical processing is carried out after all the data are received; for quickly sending all requests, the SDK does not guarantee the order of the split data, and can only distinguish the split data by i, that is, the data received last by the back end is not necessarily the data of i equal to reduce-1; each split data has a return value, and if the split data is not completely received, a code is required to be returned: 'SKIP' tells the SDK to ignore callback, only the last received data does not need all data, and the SDK carries out callback;
and returning a value:
{
"status": true,// return execution result state;
"data": any,// is used to return data to the page;
"code": "_ SKIP"// only when split;
}。
preferably, the client push interface:
URL：/push；
parameters are as follows: none;
interface types are as follows: and (4) automatic.
Preferably, the client pushing interface is automatically executed, and is automatically called after new data pushing is detected in the health interface, and the data is not 0;
and returning a value:
{
"status": true,// return result state;
"data": the any// is used for returning data to the page and packaging the service data format according to the service scene;
}。
preferably, the exit program:
URL：/exit；
parameters are as follows: none;
interface types are as follows: and (4) manually operating.
Preferably, the Exit program immediately exits the communication mode without calling the interface after clicking the Exit without detecting the client state, clicks the Exit call/Exit interface when detecting that the client state is normal, and continuously detects the client state, and exits the mode without forcing, until detecting that the client stops service, the update state is OFF, and exits the communication mode;
and returning a value:
{
"status": true,// return result state;
"data": any// is used to return data to the page;
}。
compared with the related technology, the HTTP-based webpage and local application communication protocol and application provided by the invention have the following beneficial effects:
the invention provides a communication protocol and application between a webpage and a local application based on an HTTP protocol, which are communicated by using a general HTTP protocol, can realize cross-language, cross-application and direct local communication, can directly realize communication among different applications without transferring through a server, provide extensible localization capability for the webpage, bypass the limitation of a browser by a technical means, and increase the localization capability of the existing webpage at any time without greatly modifying the original functions, replacing technical routes and adjusting the architecture, and only need to increase a service interface.
Drawings
FIG. 1 is a flowchart illustrating client-side initiation of a communication protocol and application between a web page and a local application based on the HTTP protocol according to the present invention;
fig. 2 is a flow chart of information transmission of the HTTP protocol-based web page and local application communication protocol and application provided by the present invention.
Detailed Description
The invention is further described with reference to the following figures and embodiments.
Please refer to fig. 1 and fig. 2 in combination, wherein fig. 1 is a flowchart illustrating a client-side initiation process of a communication protocol and an application between a web page and a local application based on an HTTP protocol according to the present invention; fig. 2 is a flow chart of information transmission of the HTTP protocol-based web page and local application communication protocol and application provided by the present invention. A communication protocol and application of a webpage and a local application based on an HTTP protocol comprises: the method comprises the following steps of defining a communication protocol, a webpage end communication packet and a client end communication packet; the communication protocol definition comprises a communication mode definition and a communication protocol format; the communication protocol adopted by the communication mode definition is based on an HTTP protocol, an HTTP service module is integrated by local application, the HTTP service is started, in order to ensure that the safe HTTP service only monitors 127.0.0.1 local IP and only allows local calling, a service port is 36666 by default and can be arbitrarily designated as a legal port, the safe HTTP service is started in sequence, if the safe HTTP service is started successfully, the safe HTTP service is fixed as a current port, if the safe HTTP service is started successfully, a standby port is tried, and if all port attempts fail, the safe HTTP service is stopped; the communication protocol format adopts a communication format that all communication is based on an HTTP standard, only GET requests are used for improving compatibility, all requests are sent by a webpage end, and the protocol defines four communication API interfaces including a health check interface, a command execution interface, a client push interface and an exit program; the webpage end communication packet comprises a webpage end communication packet function; the client communication packet includes a client communication packet function.
The webpage end communication packet function is as follows:
the communication function of the webpage end is realized completely based on the communication protocol, the mobile terminal browser is compatible with a mainstream PC (personal computer) and a mobile terminal browser, no third party is relied on, and development frames such as primary JS (JavaScript), JQuery, Angular, VUE (virtual eUe) and React are supported;
the method supports initialization configuration, can define program ports by self, can support detection of 1-N ports, and can poll/health ports of N ports simultaneously when a program runs, and support polling configuration, polling frequency and timeout time: defaulting for 1 second, and when detecting that one port in the N ports is successfully communicated, locking the port and stopping the detection of other ports;
supporting state detection: support for application states: the automatic tracking of three states of stopping, starting and started, the communication package will always pass/health interface detection program state, when the application program exits, the interface continuously detects communication failure for many times, automatically sets the application state as stopping and stops detection;
the JNLP mode is supported to start the JAVA program, and the JAVA program can be automatically downloaded and started by configuring the JNLP mode;
the method supports data unpacking, can customize unpack data limitation, and defaults: 8000 bytes;
and push detection is supported, and when the data detected by the/health interface is not 0, the push interface is automatically called to obtain the push data from the client.
Client communication packet functions:
the client function is realized based on the protocol, and the client function can be embedded into the existing system;
the realization of three languages of JAVA, C + +, GO has been completed at present, and more realization can be developed by following the above protocols;
cross-domain support to support multiple browsers and limit local access to augmented security;
a reflection supporting mode calls a service code, and a service scene is arbitrarily expanded through an actual single/exec interface;
and supporting unpacking data packet packing and performing service processing after receiving is finished.
The service ports also include 36667 and 36668, 36667 and 36668 as a default for standby, local HTTP services require CORS cross domain access support to be turned on.
The health check interface:
URL：/health；
parameters are as follows:
t: the time stamp is millisecond number and is automatically generated during calling;
interface types are as follows: and (4) automatic.
The health check interface is run: polling is carried out all the time once the webpage communication is started, whether the state of a local client program is normal is checked, polling is carried out once per second by default, and the timeout time is 1 second;
and returning a value:
{
"status": true,// fixed return;
"data": 0// returning a number greater than 0 when there is data to push to the front end, otherwise returning 0;
}。
the command execution interface:
URL：/exec；
parameters are as follows:
cmd: the execution command ID is used for distinguishing which kind of service is specifically executed, and different IDs are defined to realize that the same interface executes different services when the command ID is actually applied;
t: the time stamp is millisecond number and is automatically generated during calling;
bizData: converting data sent by the data into text content after JSON character strings;
uuid: the unique id of the command sent at this time is automatically generated and used for tracking the asynchronous return value and distinguishing when the command is split;
i: if the split is not needed, the transmission is not carried out, if the split is needed, the current packet is represented as the number of packets, and the sequence number is started from 0;
reduce: if the split is not needed, the transmission is not carried out, and if the split is needed, the number of the packets which are split together is represented;
interface types are as follows: and (4) manually operating.
The command of the command execution interface is initiated by a browser end and is sent to a local client program, because the maximum length of a GET request URL is about 8000 characters, when the length of sent data is overlong, splitting is needed, for the split data, uuid in each request is the same value, reduce is the number of split pieces, and i is the current i-th section; the back end receives incomplete data and can not carry out analysis operation, and logical processing is carried out after all the data are received; for quickly sending all requests, the SDK does not guarantee the order of the split data, and can only distinguish the split data by i, that is, the data received last by the back end is not necessarily the data of i equal to reduce-1; each split data has a return value, and if the split data is not completely received, a code is required to be returned: 'SKIP' tells the SDK to ignore callback, only the last received data does not need all data, and the SDK carries out callback;
and returning a value:
{
"status": true,// return execution result state;
"data": any,// is used to return data to the page;
"code": "_ SKIP"// only when split;
}。
the client side push interface:
URL：/push；
parameters are as follows: none;
interface types are as follows: and (4) automatic.
The client pushing interface is automatically executed, and is automatically called after new data pushing is detected in the health interface, and the data is not 0;
and returning a value:
{
"status": true,// return result state;
"data": the any// is used for returning data to the page and packaging the service data format according to the service scene;
}。
the exit program:
URL：/exit；
parameters are as follows: none;
interface types are as follows: and (4) manually operating.
When the Exit program does not detect the client state, the Exit program immediately exits the communication mode after clicking the Exit, does not call the interface, clicks the Exit call/Exit interface when detecting that the client state is normal, continuously detects the client state, and exits the mode without force until detecting that the client stops service, updates the state to be OFF, and exits the communication mode;
and returning a value:
{
"status": true,// return result state;
"data": any// is used to return data to the page;
}。
compared with the related technology, the HTTP-based webpage and local application communication protocol and application provided by the invention have the following beneficial effects:
the universal HTTP protocol is used for communication, cross-language, cross-application and direct local communication can be realized, communication among different applications is directly carried out, server transfer is not needed, extensible localization capability is provided for a webpage, browser limitation is avoided through technical means, localization capability is added to the existing webpage at any time, the original functions do not need to be modified in a large amount, technical routes do not need to be changed, the framework does not need to be adjusted, and only a service interface needs to be added.
The implementation case is as follows:
case one: the customer needs to read the data of local electronic scale through the serial ports and weigh in webpage end is used, because the browser can't directly read the serial ports, the traditional mode is: the program of the C/S architecture is used, serial port communication is integrated in the program, and the requirement is that the B/S architecture is not suitable; or the communication is carried out by developing a browser plug-in and a common ActiveX control, but the technology is too old and only supports an IE browser, and the IE browser fails in the latest version of operating system and has larger expected deviation with a client.
Case two: the client system is WEB application, when data is viewed in a browser, the data in the current webpage can be quickly opened in 3D design software such as local Catia and the like, and the data in the webpage is updated after the data is stored in the local software.
Case three: when a client uses a webpage end application, thousands of files need to be downloaded from a server end, and after downloading is completed, local design software is used for loading, the traditional method is that the files are downloaded one by one, batch downloading functions of some downloading software are called, or the files are packed into one file for downloading, the client needs that the files are sensitive files, third parties cannot be used for downloading the software, the number of the files is large, the files are large, and the packing and downloading effects are not good.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A communication protocol and application between a webpage and a local application based on an HTTP protocol are characterized by comprising the following steps: the method comprises the following steps of defining a communication protocol, a webpage end communication packet and a client end communication packet;
the communication protocol definition comprises a communication mode definition and a communication protocol format;
the communication protocol adopted by the communication mode definition is based on an HTTP protocol, an HTTP service module is integrated by local application, the HTTP service is started, in order to ensure that the safe HTTP service only monitors 127.0.0.1 local IP and only allows local calling, a service port is 36666 by default and can be arbitrarily designated as a legal port, the safe HTTP service is started in sequence, if the safe HTTP service is started successfully, the safe HTTP service is fixed as a current port, if the safe HTTP service is started successfully, a standby port is tried, and if all port attempts fail, the safe HTTP service is stopped;
the communication protocol format adopts a communication format that all communication is based on an HTTP standard, only GET requests are used for improving compatibility, all requests are sent by a webpage end, and the protocol defines four communication API interfaces including a health check interface, a command execution interface, a client push interface and an exit program;
the webpage end communication packet comprises a webpage end communication packet function;
the client communication packet includes a client communication packet function.
2. The HTTP protocol-based web page and local application communication protocol and application as claimed in claim 1, wherein the service ports further include 36667 and 36668, 36667 and 36668 for standby by default, and the local HTTP service requires CORS cross-domain access support to be turned on.
3. The HTTP protocol-based web page and native application communication protocol and application of claim 1, wherein the health check interface:
URL：/health；
parameters are as follows:
t: the time stamp is millisecond number and is automatically generated during calling;
interface types are as follows: and (4) automatic.
4. The HTTP protocol-based web page and native application communication protocol and application of claim 3, wherein the health check interface is operable to: polling is carried out all the time once the webpage communication is started, whether the state of a local client program is normal is checked, polling is carried out once per second by default, and the timeout time is 1 second;
and returning a value:
{
"status": true,// fixed return;
"data": 0// returning a number greater than 0 when there is data to push to the front end, otherwise returning 0;
}。
5. the HTTP protocol-based web page and native application communication protocol and application of claim 1, wherein the command execution interface:
URL：/exec；
parameters are as follows:
cmd: the execution command ID is used for distinguishing which kind of service is specifically executed, and different IDs are defined to realize that the same interface executes different services when the command ID is actually applied;
t: the time stamp is millisecond number and is automatically generated during calling;
bizData: converting data sent by the data into text content after JSON character strings;
uuid: the unique id of the command sent at this time is automatically generated and used for tracking the asynchronous return value and distinguishing when the command is split;
i: if the split is not needed, the transmission is not carried out, if the split is needed, the current packet is represented as the number of packets, and the sequence number is started from 0;
reduce: if the split is not needed, the transmission is not carried out, and if the split is needed, the number of the packets which are split together is represented;
interface types are as follows: and (4) manually operating.
6. The HTTP protocol-based web page and local application communication protocol and application of claim 5, wherein the command of the command execution interface is initiated by a browser to send a command to a local client program, since the maximum length of the GET request URL is about 8000 characters, when the length of the sent data is too long, splitting is required, for the split data, uuid in each request is the same value, reduce is the number of split pieces, and i is the current i-th segment; the back end receives incomplete data and can not carry out analysis operation, and logical processing is carried out after all the data are received; for quickly sending all requests, the SDK does not guarantee the order of the split data, and can only distinguish the split data by i, that is, the data received last by the back end is not necessarily the data of i equal to reduce-1; each split data has a return value, and if the split data is not completely received, a code is required to be returned: 'SKIP' tells the SDK to ignore callback, only the last received data does not need all data, and the SDK carries out callback;
and returning a value:
{
"status": true,// return execution result state;
"data": any,// is used to return data to the page;
"code": "_ SKIP"// only when split;
}。
7. the HTTP protocol-based web page and local application communication protocol and application of claim 1, wherein the client push interface:
URL：/push；
parameters are as follows: none;
interface types are as follows: and (4) automatic.
8. The HTTP protocol-based web page and local application communication protocol and application of claim 7, wherein the client push interface is automatically executed, and is automatically invoked when a new data push is detected in the health interface, and the data is not 0;
and returning a value:
{
"status": true,// return result state;
"data": the any// is used for returning data to the page and packaging the service data format according to the service scene;
}。
9. the HTTP protocol-based web page and native application communication protocol and application of claim 1, wherein the exit program:
URL：/exit；
parameters are as follows: none;
interface types are as follows: and (4) manually operating.
10. The HTTP protocol-based web page and local application communication protocol and application of claim 9, wherein the Exit program exits the communication mode immediately after clicking the Exit without detecting the client state, does not invoke the interface, clicks the Exit invocation/Exit interface when detecting that the client state is normal, and continues to detect the client state, exits the mode without force, updates the state to OFF and exits the communication mode until detecting that the client stops the service;
and returning a value:
{
"status": true,// return result state;
"data": any// is used to return data to the page;
}。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011008148.1A CN112214333B (en) | 2020-09-23 | 2020-09-23 | Method for applying HTTP protocol-based webpage and local application communication protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011008148.1A CN112214333B (en) | 2020-09-23 | 2020-09-23 | Method for applying HTTP protocol-based webpage and local application communication protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112214333A true CN112214333A (en) | 2021-01-12 |
| CN112214333B CN112214333B (en) | 2023-08-22 |
Family
ID=74050876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011008148.1A Active CN112214333B (en) | 2020-09-23 | 2020-09-23 | Method for applying HTTP protocol-based webpage and local application communication protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214333B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090129378A1 (en) * | 2007-11-20 | 2009-05-21 | International Business Machines Corporation | Surreptitious web server bias towards desired browsers |
| US8965952B1 (en) * | 2009-09-22 | 2015-02-24 | Cellco Partnership | Processing service requests of multiple types on a common communication port for a service that accepts only one type |
| CN105471824A (en) * | 2014-09-03 | 2016-04-06 | 阿里巴巴集团控股有限公司 | Method, device and system for invoking local service assembly by means of browser |
| US20160191633A1 (en) * | 2014-12-31 | 2016-06-30 | Guangzhou Ucweb Computer Technology Co., Ltd. | Method and apparatus for implementing communication from web page to client |
| CN107959727A (en) * | 2017-12-14 | 2018-04-24 | 腾讯科技（深圳）有限公司 | The method and device communicated between webpage and client |
| CN109756501A (en) * | 2019-01-02 | 2019-05-14 | 中国科学院信息工程研究所 | A kind of high concealment network agent method and system based on http protocol |
-
2020
- 2020-09-23 CN CN202011008148.1A patent/CN112214333B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090129378A1 (en) * | 2007-11-20 | 2009-05-21 | International Business Machines Corporation | Surreptitious web server bias towards desired browsers |
| US8965952B1 (en) * | 2009-09-22 | 2015-02-24 | Cellco Partnership | Processing service requests of multiple types on a common communication port for a service that accepts only one type |
| CN105471824A (en) * | 2014-09-03 | 2016-04-06 | 阿里巴巴集团控股有限公司 | Method, device and system for invoking local service assembly by means of browser |
| US20160191633A1 (en) * | 2014-12-31 | 2016-06-30 | Guangzhou Ucweb Computer Technology Co., Ltd. | Method and apparatus for implementing communication from web page to client |
| CN105812345A (en) * | 2014-12-31 | 2016-07-27 | 广州市动景计算机科技有限公司 | Method and device for realizing communication between webpage and client end |
| CN107959727A (en) * | 2017-12-14 | 2018-04-24 | 腾讯科技（深圳）有限公司 | The method and device communicated between webpage and client |
| CN109756501A (en) * | 2019-01-02 | 2019-05-14 | 中国科学院信息工程研究所 | A kind of high concealment network agent method and system based on http protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214333B (en) | 2023-08-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5828840A (en) | Server for starting client application on client if client is network terminal and initiating client application on server if client is non network terminal | |
| US6938087B1 (en) | Distributed universal communication module for facilitating delivery of network services to one or more devices communicating over multiple transport facilities | |
| US5926636A (en) | Remote procedural call component management method for a heterogeneous computer network | |
| US6405367B1 (en) | Apparatus and method for increasing the performance of Java programs running on a server | |
| US7516178B1 (en) | Communicating messages between components in a client/server environment using a object broker | |
| US6542908B1 (en) | Technique for automatically and transparently transforming software components into software components capable of execution in a client/server computing environment | |
| TWI767182B (en) | H5-Based Access Components and Mobile Terminals | |
| US6874021B1 (en) | Techniques for configuring network devices with consistent forms for getting and setting device properties | |
| US6163797A (en) | Application dispatcher for seamless, server application support for network terminals and non-network terminals | |
| KR20050091030A (en) | System and method for building and execution of platform-neutral generic services' client applications | |
| US20130219411A1 (en) | Device Connectivity Framework | |
| CN108829398B (en) | Mobile terminal page interaction realization method and device | |
| US11709722B2 (en) | Extensible communication framework and communication method supporting multiple communication protocols | |
| US9450826B2 (en) | Device connectivity framework | |
| EP3797356B1 (en) | Code base sharing between standalone and web-based versions of an application due to the implementing of an emulated network communication channel | |
| EP1164482B1 (en) | System and method for interactive communication between objects in a distributed computing environment | |
| US9026701B2 (en) | Implementing device support in a web-based enterprise application | |
| WO2005050406A2 (en) | Server visualization and control | |
| EP1562115A2 (en) | Socket connections over a serial link | |
| CN112688915A (en) | Cross-protocol communication method, device and server | |
| WO2023083071A1 (en) | View interaction method and apparatus, electronic device, and computer readable medium | |
| CN112214333A (en) | Webpage and local application communication protocol based on HTTP (hyper text transport protocol) and application | |
| US7908397B1 (en) | Application server gateway technology | |
| WO2003024054A2 (en) | Inbound connector | |
| KR100494827B1 (en) | Distributed object model based radio server with hardware-independent communication interface and communication control method using the same |
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 |