CN112214333B - Method for applying HTTP protocol-based webpage and local application communication protocol - Google Patents
Method for applying HTTP protocol-based webpage and local application communication protocol Download PDFInfo
- Publication number
- CN112214333B CN112214333B CN202011008148.1A CN202011008148A CN112214333B CN 112214333 B CN112214333 B CN 112214333B CN 202011008148 A CN202011008148 A CN 202011008148A CN 112214333 B CN112214333 B CN 112214333B
- Authority
- CN
- China
- Prior art keywords
- communication
- data
- interface
- client
- protocol
- 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
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 method for applying a web page based on an HTTP protocol and a local application communication protocol. The method for applying the HTTP-based webpage and the local application communication protocol comprises the following steps: communication protocol definition, 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 mode definition adopts a communication protocol based on the HTTP protocol. The method for applying the HTTP-based webpage and the local application communication protocol has the advantages that the general HTTP protocol is used for communication, the communication can be carried out across languages and applications, the local communication is direct, the communication between different applications is direct, the server transfer is not needed, the expandable localization capability is provided for the webpage, the browser limit is bypassed through the technical means, the localization capability is added to the existing webpage at any time, the original functions are not required to be modified in a large amount, the technical route is not required to be replaced, the architecture is not required to be adjusted, and the service interface is only required to be added.
Description
Technical Field
The invention relates to the field of computer software, in particular to a method for applying a web page based on an HTTP protocol and a local application communication protocol.
Background
At present, a plurality of local application programs are available on the market, including various operating systems, various development languages, finished products or self-research, due to influences of technical capability, frame technical limitation, development time and the like, although part of software supports extended development, the whole experience is not very good especially on UI interaction, and due to large technical difference, development cost is very high, in addition, a new software platform depends on a browser based on a BS architecture, but limited access to local resources due to browser limitation exists, some local applications either need to be newly framed for development, investment cost is huge, or development of a mixed mode cannot be achieved, good integration with existing mature local applications cannot be achieved, in addition, good data communication cannot be achieved between different local applications if a communication mode is not defined at first, and later, if communication needs to be carried out, higher development cost is needed.
At present, no technology for directly communicating a webpage with a local application is realized, and the technology is complicated in architecture by a server transfer mode or a hybrid mode through a self-defined APP or browser mode, namely, a program or part of an earlier program has no network access function and is difficult to modify.
Therefore, it is necessary to provide a method for applying the HTTP-based web page and the native application communication protocol to solve the above technical problems.
Disclosure of Invention
The invention provides a method for applying a communication protocol between a web page based on an HTTP protocol and a local application, which solves the technical problem that no web page is directly communicated with the local application.
In order to solve the technical problem, the method for applying the communication protocol between the web page based on the HTTP and the local application provided by the invention comprises the following steps: communication protocol definition, 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 mode is defined that the adopted communication protocol is based on the HTTP protocol, a local application integrates an HTTP service module and starts HTTP service, so that the safety HTTP service only monitors the local IP of 127.0.0.1, only allows local calling, a service port defaults to 36666, can be arbitrarily designated as a legal port, tries to start in sequence, is fixed as a current port if the starting is successful, tries to reserve ports if the starting is conflicted, and stops starting if all port attempts fail; the communication protocol format adopts a communication format based on 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 in total, including a health check interface, a command execution interface, a client push interface and an exit program;
the webpage end communication package comprises a webpage end communication package function;
the client communication package includes a client communication package function.
Preferably, the service port further includes 36667 and 36668, 36667 and 36668 for standby, and the local HTTP service needs to turn on the CORS cross-domain access support.
Preferably, the health check interface:
URL：/health；
parameters:
t: time stamp millisecond number, automatic generation when calling;
interface type: and (5) automatically.
Preferably, the health check interface is operative to: once the webpage communication is started, polling is carried out all the time, whether the local client program is in a normal state is checked, the polling is carried out every second by default, and the timeout time is 1 second;
return value:
{
"status": true,// fixed return;
"data": 0// return a number greater than 0 when there is data push to the front end, otherwise return 0;
}。
preferably, the command execution interface:
URL：/exec；
parameters:
cmd: the execution command ID is used for distinguishing which service is executed specifically, and different services can be executed by the same interface by defining different IDs in actual application;
t: time stamp millisecond number, automatic generation when calling;
bizData: converting the data transmitted by the data into text contents after JSON character strings;
uuid: the unique id of the sending command is automatically generated and used for tracking an asynchronous return value and distinguishing when the command is split;
i: if the packet is not required to be split, the packet is not transmitted, and if the packet is required to be split, the packet is represented as the current packet, and the sequence number starts from 0;
reduction: if the packets are not required to be split, the packets are not transmitted, and if the packets are required to be split, the packets represent the number of packets which are split together;
interface type: and (5) manual operation.
Preferably, the command of the command execution interface is initiated by the browser end, and a command is sent to the local client program, and as the maximum length of the GET request URL is about 8000 characters, when the sending data length is very long, splitting is needed, and for the split data, uuid in each request is the same value, reduce is the number of split, and i is the current i-th segment; the back end receives incomplete data and can not carry out analysis operation, and logic processing is carried out after all data are received; for quickly sending all requests, the SDK does not guarantee the sequence of the split data, but can only distinguish by i, i.e. the last received data at the back end is not necessarily i=reduce-1; each time the split data needs to have a return value, if not all received, the "code" needs to be returned: "_SKIP", tells the SDK to ignore the callback, only the last received piece of data does not need all data, and the SDK performs callback;
return value:
{
"status": true,// returns the execution result status;
"data": any,// is used to return data to the page;
"code": "_SKIP"// only when split;
}。
preferably, the client pushes an interface:
URL：/push；
parameters: the method is free;
interface type: and (5) automatically.
Preferably, the client push interface is automatically executed, and when new data push is detected in the health interface, the client push interface is automatically called, and the data is not 0;
return value:
{
"status": true,// return result status;
"data": any// is used for returning data to the page, and the business data format is packaged according to the business scene;
}。
preferably, the exit procedure:
URL：/exit；
parameters: the method is free;
interface type: and (5) manual operation.
Preferably, the Exit program immediately exits the communication mode after clicking the Exit after detecting no client state, does not call the interface, clicks the Exit call/Exit interface when detecting that the client state is normal, continuously detects the client state, does not force the Exit mode, and updates the state to OFF and exits the communication mode until detecting that the client stops service;
return value:
{
"status": true,// return result status;
"data": any// is used to return data to the page;
}。
compared with the related art, the method for applying the HTTP protocol-based webpage and the local application communication protocol has the following beneficial effects:
the invention provides a method for applying a communication protocol between a web page based on an HTTP protocol and a local application, which uses the general HTTP protocol to communicate, can directly communicate locally across languages and applications, and can directly communicate between different applications without transferring through a server, so as to provide expandable localization capability for the web page, bypass the limitation of a browser through a technical means, add localization capability to the existing web page at any time, and do not need to largely modify the original functions, change the technical route, adjust the architecture and only increase a service interface.
Drawings
FIG. 1 is a client side startup flow chart of a method for applying HTTP protocol-based web pages and local application communication protocols provided by the invention;
fig. 2 is a flowchart of information transmission of a method for applying HTTP-based web pages and native application communication protocols according to the present invention.
Description of the embodiments
The invention will be further described with reference to the drawings and embodiments.
Referring to fig. 1 and fig. 2 in combination, fig. 1 is a flowchart of client start-up of a method for applying HTTP-based web pages and native application communication protocols according to the present invention; fig. 2 is a flowchart of information transmission of a method for applying HTTP-based web pages and native application communication protocols according to the present invention. A method for applying a web page based on HTTP protocol and a local application communication protocol comprises the following steps: communication protocol definition, 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 mode is defined that the adopted communication protocol is based on the HTTP protocol, a local application integrates an HTTP service module and starts HTTP service, so that the safety HTTP service only monitors the local IP of 127.0.0.1, only allows local calling, a service port defaults to 36666, can be arbitrarily designated as a legal port, tries to start in sequence, is fixed as a current port if the starting is successful, tries to reserve ports if the starting is conflicted, and stops starting if all port attempts fail; the communication protocol format adopts a communication format based on 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 in total, including a health check interface, a command execution interface, a client push interface and an exit program; the webpage end communication package comprises a webpage end communication package function; the client communication package includes a client communication package function.
Webpage end communication package function:
the webpage end communication function is realized completely based on the communication protocol, the webpage end communication function is compatible with a main stream PC and a mobile end browser, no third party dependence exists, and development frameworks such as a primary JS, a JQuery, an Angular, a VUE, a reaction and the like are supported;
the initialization configuration is supported, the program ports can be customized, 1-N port detection can be supported, and when the program runs, the N ports/health ports are simultaneously polled, the polling configuration is supported, the polling frequency and the timeout time are supported: default 1 second, when one of the N ports is detected to be successful in communication, the port is locked, and detection of other ports is stopped;
support state detection: supporting application state: when the application program exits, the interface continuously detects communication failure for a plurality of times, automatically sets the application state as a stop, and stops detection;
the JNLP mode is supported to start the JAVA program, and the JNLP mode can be configured to automatically download and start the JAVA program;
support data unpacking, and can self-define unpacking data limitation, defaults: 8000 bytes;
and supporting push detection, and when the/health interface detects that the data is not 0, automatically calling/push interface to acquire push data from the client.
Client communication packet function:
the client function is realized based on the above protocol, and the existing system can be embedded;
the realization of JAVA, C++, GO is completed at present, the protocols can be followed, and more realization can be developed;
supporting cross-domain to support multiple browsers and limiting local access to the extension security;
the service codes are called in a supporting reflection mode, so that the service scene is arbitrarily expanded through an actual single/exec interface;
and supporting unpacking the data group package, and carrying out service processing after the receiving is finished.
The service port also includes 36667 and 36668, 36667 and 36668 for standby, and the local HTTP service needs to turn on the CORS cross-domain access support.
The health check interface:
URL：/health；
parameters:
t: time stamp millisecond number, automatic generation when calling;
interface type: and (5) automatically.
The health check interface is operative to: once the webpage communication is started, polling is carried out all the time, whether the local client program is in a normal state is checked, the polling is carried out every second by default, and the timeout time is 1 second;
return value:
{
"status": true,// fixed return;
"data": 0// return a number greater than 0 when there is data push to the front end, otherwise return 0;
}。
the command execution interface:
URL：/exec；
parameters:
cmd: the execution command ID is used for distinguishing which service is executed specifically, and different services can be executed by the same interface by defining different IDs in actual application;
t: time stamp millisecond number, automatic generation when calling;
bizData: converting the data transmitted by the data into text contents after JSON character strings;
uuid: the unique id of the sending command is automatically generated and used for tracking an asynchronous return value and distinguishing when the command is split;
i: if the packet is not required to be split, the packet is not transmitted, and if the packet is required to be split, the packet is represented as the current packet, and the sequence number starts from 0;
reduction: if the packets are not required to be split, the packets are not transmitted, and if the packets are required to be split, the packets represent the number of packets which are split together;
interface type: and (5) manual operation.
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 a GET request URL is about 8000 characters, when the length of sent data is very long, splitting is needed, and for the split data, uuid in each request is the same value, reduce is the number of split, and i is the current i-th segment; the back end receives incomplete data and can not carry out analysis operation, and logic processing is carried out after all data are received; for quickly sending all requests, the SDK does not guarantee the sequence of the split data, but can only distinguish by i, i.e. the last received data at the back end is not necessarily i=reduce-1; each time the split data needs to have a return value, if not all received, the "code" needs to be returned: "_SKIP", tells the SDK to ignore the callback, only the last received piece of data does not need all data, and the SDK performs callback;
return value:
{
"status": true,// returns the execution result status;
"data": any,// is used to return data to the page;
"code": "_SKIP"// only when split;
}。
the client pushes an interface:
URL：/push；
parameters: the method is free;
interface type: and (5) automatically.
The client pushing interface is automatically executed, and when new data pushing is detected in the health interface, the client pushing interface is automatically called, and the data is not 0;
return value:
{
"status": true,// return result status;
"data": any// is used for returning data to the page, and the business data format is packaged according to the business scene;
}。
the exit program:
URL：/exit；
parameters: the method is free;
interface type: and (5) manual operation.
The Exit program immediately exits the communication mode after clicking the Exit after detecting the state of the client, does not call the interface, clicks the Exit call/Exit interface when detecting the state of the client is normal, continuously detects the state of the client, does not force the Exit mode, and updates the state to be OFF and exits the communication mode until detecting that the client stops serving;
return value:
{
"status": true,// return result status;
"data": any// is used to return data to the page;
}。
compared with the related art, the method for applying the HTTP protocol-based webpage and the local application communication protocol has the following beneficial effects:
the universal HTTP protocol communication is used, so that the universal HTTP protocol communication can be used for cross-language and cross-application, direct local communication and communication between different applications can be directly carried out without transferring through a server, the expandable localization capability is provided for the webpage, the browser limitation is bypassed through the 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 replaced, the framework is not required to be adjusted, and the service interface is only required to be added.
Implementation case:
case one: the client needs to read the data of the local electronic scale through the serial port for weighing in the application of the webpage end, and the browser cannot directly read the serial port, so that the traditional mode is as follows: integrating serial communication in a program by using a program of a C/S architecture, wherein 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 has failed in the latest version of operating system and has larger deviation with the expected of a client.
Case two: the client system is a WEB application, when data is checked in a browser, the data in a current webpage can be quickly opened in 3D design software such as a local Catia, and after the local software is stored, the data in the webpage is updated.
Case three: when a client uses a webpage end application, thousands of files need to be downloaded from a server end, after the downloading is completed, local design software is used for loading, the files are downloaded one by one, batch downloading functions of some downloading software are called, or the files are packaged into one file for downloading, the client needs that the files are sensitive files, the software cannot be downloaded by a third party, the number of the files is large, the packaging downloading effect is poor, the uploading and downloading of the files can be controlled on the webpage end by integrating the method in a self-developed file uploading and downloading tool, uploading and downloading state monitoring, starting and stopping and the like are performed, and after the downloading is completed, the local design program is started automatically to open the corresponding files.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent structures or equivalent processes or direct or indirect application in other related technical fields are included in the scope of the present invention.
Claims (7)
1. A method for applying a web page based on HTTP protocol and a local application communication protocol, comprising: communication protocol definition, 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 mode is defined that the adopted communication protocol is based on the HTTP protocol, a local application integrates an HTTP service module and starts HTTP service, so that the safety HTTP service only monitors the local IP of 127.0.0.1, only allows local calling, a service port defaults to 36666, can be arbitrarily designated as a legal port, tries to start in sequence, is fixed as a current port if the starting is successful, tries to reserve ports if the starting is conflicted, and stops starting if all port attempts fail;
the communication protocol format adopts a communication format based on 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 in total, including a health check interface, a command execution interface, a client push interface and an exit program;
the webpage end communication package comprises a webpage end communication package function;
the client communication package comprises a client communication package function;
the health check interface is operative to: once the webpage communication is started, polling is carried out all the time, whether the local client program is in a normal state is checked, the polling is carried out every second by default, and the timeout time is 1 second;
return value:
{
"status": true,// fixed return;
"data": 0// return a number greater than 0 when there is data push to the front end, otherwise return 0;
}；
the command execution interface:
URL：/exec；
parameters:
cmd: the execution command ID is used for distinguishing which service is executed specifically, and different services can be executed by the same interface by defining different IDs in actual application;
t: time stamp millisecond number, automatic generation when calling;
bizData: converting the data transmitted by the data into text contents after JSON character strings;
uuid: the unique id of the sending command is automatically generated and used for tracking an asynchronous return value and distinguishing when the command is split;
i: if the packet is not required to be split, the packet is not transmitted, and if the packet is required to be split, the packet is represented as the current packet, and the sequence number starts from 0;
reduction: if the packets are not required to be split, the packets are not transmitted, and if the packets are required to be split, the packets represent the number of packets which are split together;
interface type: manually;
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 a GET request URL is about 8000 characters, when the length of sent data is very long, splitting is needed, the uuid in each request is the same value for the split data, the reduce is the number of split strips, and i is the current i-th segment; the back end receives incomplete data and can not carry out analysis operation, and logic processing is carried out after all data are received; for quickly sending all requests, the SDK does not guarantee the sequence of the split data, but can only distinguish by i, i.e. the last received data at the back end is not necessarily i=reduce-1; each time the split data needs to have a return value, if not all received, the "code" needs to be returned: "_SKIP", telling the SDK to ignore the callback, and only the last piece of received data does not need all data, and the SDK performs callback;
return value:
{
"status": true,// returns the execution result status;
"data": any,// is used to return data to the page;
"code": "_SKIP"// only when split;
}。
2. the method of claim 1, wherein the service port further comprises 36667 and 36668, 36667 and 36668 for standby, and the local HTTP service requires opening CORS cross-domain access support.
3. The method of claim 1, wherein the health check interface:
URL：/health；
parameters:
t: time stamp millisecond number, automatic generation when calling;
interface type: and (5) automatically.
4. The method of claim 1, wherein the client pushes an interface:
URL：/push；
parameters: the method is free;
interface type: and (5) automatically.
5. The method for applying HTTP-based web pages and native application communication protocols according to claim 4, wherein the client push interface is automatically executed, and is automatically invoked when new data push is detected in the health interface, and data is not 0;
return value:
{
"status": true,// return result status;
"data": any// is used for returning data to the page, and the business data format is packaged according to the business scene;
}。
6. the method of claim 1, wherein the exit program:
URL：/exit；
parameters: the method is free;
interface type: and (5) manual operation.
7. The method for applying HTTP protocol-based web pages and native application communication protocols according to claim 6, wherein the Exit program immediately exits the communication mode after detecting no client state, clicks Exit, does not invoke the interface, clicks Exit invoke/Exit interface when detecting that the client state is normal, and continues to detect the client state, and does not force the Exit mode until detecting that the client is out of service, updates the state to OFF, and exits the communication mode;
return value:
{
"status": true,// return result status;
"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 CN112214333A (en) | 2021-01-12 |
| CN112214333B true 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 (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8244879B2 (en) * | 2007-11-20 | 2012-08-14 | International Business Machines Corporation | Surreptitious web server bias towards desired browsers |
-
2020
- 2020-09-23 CN CN202011008148.1A patent/CN112214333B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
|---|---|
| CN112214333A (en) | 2021-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6938087B1 (en) | Distributed universal communication module for facilitating delivery of network services to one or more devices communicating over multiple transport facilities | |
| US6405367B1 (en) | Apparatus and method for increasing the performance of Java programs running on a server | |
| AU730088B2 (en) | A system, method and article of manufacture for seamless, server application support of network and non-network client terminals | |
| US5926636A (en) | Remote procedural call component management method for a heterogeneous computer network | |
| US7516178B1 (en) | Communicating messages between components in a client/server environment using a object broker | |
| US6874021B1 (en) | Techniques for configuring network devices with consistent forms for getting and setting device properties | |
| CN111176761B (en) | Micro-service calling method and device | |
| US20020016790A1 (en) | Apparatus and method for dynamically verifying information in a distributed system | |
| US20020199036A1 (en) | Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system | |
| KR20010041293A (en) | Method and apparatus for remote method invocation | |
| CN107678778B (en) | Hybrid-based compatible method, adapter, operation device and system | |
| EP0978976B1 (en) | A method and system for an application dispatcher for server application | |
| US6141793A (en) | Apparatus and method for increasing the performance of interpreted programs running on a server | |
| KR20110065448A (en) | Composing message processing pipelines | |
| US10353700B1 (en) | Code base sharing between standalone and web-based versions of an application via an emulated network communication channel | |
| US9026701B2 (en) | Implementing device support in a web-based enterprise application | |
| CN112214333B (en) | Method for applying HTTP protocol-based webpage and local application communication protocol | |
| 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 | |
| US7908397B1 (en) | Application server gateway technology | |
| WO2021233103A1 (en) | Method and apparatus of cross-ipc access | |
| WO1999044123A1 (en) | Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system | |
| CN114257576A (en) | RPC server implementation method based on support of multiple communication protocols | |
| CN107623704B (en) | Data interaction method in terminal equipment, client and browser |
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 |