CN111552488A - Method and storage medium for H5 cross-engine client data automation updating - Google Patents
Method and storage medium for H5 cross-engine client data automation updating Download PDFInfo
- Publication number
- CN111552488A CN111552488A CN201910109573.0A CN201910109573A CN111552488A CN 111552488 A CN111552488 A CN 111552488A CN 201910109573 A CN201910109573 A CN 201910109573A CN 111552488 A CN111552488 A CN 111552488A
- Authority
- CN
- China
- Prior art keywords
- request
- http
- callback function
- result
- class
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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]
Abstract
The invention provides a method and a storage medium for H5 cross-engine client data automatic updating, wherein the method comprises the following steps: an application layer of the client calls an Http manager to initiate an Http request to the server; the Http manager creates a corresponding Http class according to the Http request, and initiates the Http request to a server according to the Http class, wherein the Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager; and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer. The invention can not only realize the monitoring and the automatic updating of the data change of the server data of the HTTP/HTTPS short link communication; and the operation process is greatly simplified, and meanwhile, the data distribution and maintenance cost is reduced.
Description
Technical Field
The invention relates to the field of data proxy, in particular to a method and a storage medium for H5 cross-engine client data automatic updating.
Background
In the current H5 application development, specifically, for example, H5 game development, a TypeScript, an ActionScript, or a JavaScript language is mostly used for project development; the communication mode with the server side mostly uses HTTP/HTTPS short link or WebSocket long link. Therefore, there is a large cost in client data maintenance.
This is because: 1. the TypeScript, ActionScript and JavaScript languages themselves do not provide data broker-like functionality to dynamically support data updates; 2. the data maintenance cost of the client to the server is high. Data interaction related work such as data return, monitoring, modification, deletion, interface updating and the like aiming at different types of communication modes mostly needs to realize respective service data managers according to different services.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the H5 cross-engine client data automatic updating method and the storage medium are provided, so that the automatic updating of data change when the client communicates with the server by adopting an HTTP/HTTPS short link is realized, and the data maintenance cost and the operation complexity are greatly reduced.
In order to solve the technical problems, the invention adopts the technical scheme that:
h5 method for automatically updating data across engine clients, comprising:
an application layer of the client calls an Http manager to initiate an Http request to the server;
the Http manager creates a corresponding Http class according to the Http request, and initiates the Http request to a server according to the Http class, wherein the Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager;
and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer.
The invention provides another technical scheme as follows:
a computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, is capable of carrying out the steps involved in the above-described method for automated updating of data across engine clients of H5.
The invention has the beneficial effects that: the invention can use the HTTP/HTTPs short link communication between the client and the server for data update, and uses the HTTP manager as a bridge for connecting the application layer (client) and the communication layer, and realizes the callback and dispatch of the server data and the data update of the application layer by using the request result device. The invention realizes the monitoring of the data of the server and the monitoring from automatic updating to mounting without manually distributing the data change monitoring; various complex management classes are not used for realizing data maintenance in an application layer; not only greatly simplifying the operation process; and greatly reduces the cost of data distribution and maintenance.
Drawings
FIG. 1 is a flowchart illustrating a method for H5 cross-engine client data automation update according to an embodiment of the present invention;
fig. 2 is an interaction diagram of automatic update of server data change based on Http request according to an embodiment of the present invention.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The most key concept of the invention is as follows: aiming at the data updating condition of adopting HTTP/HTTPS short link communication between a client and a server, an HTTP manager is used as a connection bridge between an application layer (client) and a communication layer, and callback distribution of server data and data updating of the application layer are realized by means of a request result device.
The technical terms related to the invention are explained as follows:
referring to fig. 1 and 2, the present invention provides a method for H5 cross-engine client data automatic update, including:
an application layer of the client calls an Http manager to initiate an Http request to the server;
the Http manager creates a corresponding Http class according to the Http request, and initiates the Http request to a server according to the Http class, wherein the Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager;
and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer.
From the above description, the beneficial effects of the present invention are: the latest result of data change can be output to the presentation layer by means of the Http manager of the application layer, for the application party, the setting of a plurality of processors is only needed to be realized on the basis of basic data, all data streams can be automatically updated to the application, the application party does not need to spend more energy to construct a complicated and huge data management class for each data, and only needs to perform presentation according to the latest data in a specific application layer, so that the operation process is greatly simplified, and the cost of data updating and maintenance is reduced.
Furthermore, an Http request queue is built in the Http manager, and the Http request queue takes the sequence id of the Http request as a key value and stores Http classes corresponding to the Http request as a value;
the Http class is also embedded with a sequence id of the Http request.
As can be seen from the above description, in a specific embodiment, for different Http requests, the sequence id and the mapping relationship between the corresponding Http class are recorded in the Http request queue, so that not only different Http requests can be managed conveniently, but also the corresponding Http class can be obtained quickly according to the sequence id.
Further, the request result callback function includes a request success callback function and a request failure callback function;
the method further comprises the following steps:
creating an Http request result processor, wherein an abstract and general Http request result callback function and a scope are built in the Http request result processor;
the Http manager obtains a request result of the Http request from a server according to the request result callback function, and returns the request result to an application layer, specifically:
the Http request result processor acquires a request result of the Http request from the server according to a general Http request result callback function, and sends the request result of the Http request to the Http class of the Http manager;
if the request result corresponds to the request success, the Http class constructs a Http request success handler corresponding to the Http request, and the Http request success handler includes the request success callback function;
if the request result corresponds to a request failure, the Http class constructs a Http request failure processor corresponding to the Http request, wherein the Http request failure processor comprises the request failure callback function;
and the Http manager executes a request success callback function in the Http request success processor or a request failure callback function in the Http request failure processor, and sends the request result to the application layer through the request success callback function or the request failure callback function.
As can be seen from the above description, in a specific embodiment, for two request results (request failure and request success), different processors are respectively constructed, and then the callback function in the processor is used to implement the data acquisition.
Further, a request method comprising a get request method and a post request method is built in the Http manager; the parameters of the get request method comprise a url address, a scope, a request success callback function and a request failure callback function; the parameters of the post request method comprise a url address, data, a scope, a request success callback function and a request failure callback function;
the Http class is also internally provided with a scope of the request result callback function and a request method for calling the Http request by an application layer;
when an application layer calls a get request method in an Http manager to send an Http request to a server, a built-in request method in the Http class is a get method, and the request result callback function includes a request success callback function and a request failure callback function of the get request method;
when an application layer calls a post request method in an Http manager to send an Http request to a server, a request method built in the Http class is a post method, and the request result callback function includes a request success callback function or a request failure callback function of the get request method.
As can be seen from the above description, in one embodiment, two request modes for Http request are as follows: the get request mode and the post request mode are respectively embedded with corresponding request methods in the Http class, and then the Http manager calls the corresponding request methods to initiate Http requests, so that requested data can be obtained in the callbacks and immediately updated to the application layer.
Further, if the built-in request method in the Http class is a get method, the request result received by the Http class corresponds to a parameter of the get request method;
if the request method built in the Http class is a post method, the request result received by the Http class corresponds to a parameter of the post request method;
and the Http class constructs and obtains the Http request success handler or the Http request failure handler according to the scope recorded in the received request result and the request success callback or the request failure callback parameter.
As can be seen from the above description, the parameter format of the request result is set to correspond to the specific request mode, so that the Http class can quickly obtain the specified parameters in the request result to construct the Http request success handler or the Http request failure handler.
Further, the method also comprises the following steps:
the sequence id of an Http request in the Http request queue is removed by the Http manager.
According to the description, the method can also support the flexible and convenient removal of the requests which do not need monitoring and automatic updating any more, so as to avoid resource occupation and optimize the efficiency of the client for automatic updating.
The invention provides another technical scheme as follows:
a computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, is capable of carrying out the steps involved in the above-described method for automated updating of data across engine clients of H5.
From the above description, the beneficial effects of the present invention are: it can be understood by those skilled in the art that all or part of the processes in the above technical solutions can be implemented by instructing related hardware through a computer program, where the program can be stored in a computer readable storage medium, and when the program is executed, the program can include the processes of the above methods, so as to implement a data update situation for using HTTP/HTTPs short link communication between a client and a server, and implement callback distribution of server data and data update of an application layer by using an HTTP manager as a connection bridge between the application layer (client) and a communication layer, and using a request result device. The monitoring of the data of the server side and the monitoring from automatic updating to mounting are realized, and the data change monitoring is not required to be manually distributed; various complex management classes are not used for realizing data maintenance in an application layer; not only greatly simplifying the operation process; and greatly reduces the cost of data distribution and maintenance.
Example one
Referring to fig. 1 and 2, the present embodiment provides a method for automatically updating H5 data across engine clients, and for a data communication manner, i.e., HTTP/HTTPs short link communication between a client and a server, an HTTP manager is used as a bridge for connecting an application layer and a communication layer, and a request result processor is used to implement callback distribution of a result and data update of the application layer.
The method comprises the following steps:
s1: an application layer of the client calls an Http manager to initiate an Http request to the server;
s2: after receiving an Http request sent by an application layer, an Http manager creates a corresponding Http class according to the Http request, and sends the Http request to a server according to the Http class, wherein the Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager;
s3: and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer.
Example two
Referring to fig. 1 and fig. 2, the present embodiment corresponds to the first embodiment, and is further limited:
first, early construction
1. Creating an HTTP request result processor HttpHandler;
the built-in variables comprise callback functions and scope after Http requests for abstract public use; specifically, a callback function and scope for request success and a callback function and scope for request failure can be set.
2. Creating an Http class;
it is used as the base class of HTTP requests, with the built-in variables: a request sequence id, an http request, a request success callback (binding http), a request failure callback (binding http), a scope, a request method, a return type, a header, reconnection times, a get method, a post method, and the like;
the method comprises the following steps: the post method, the get method;
3. creating an Http manager;
a variable Http request queue is built in (the request sequence id is used as a key value, and an Http class is stored as a value);
the method comprises the following steps:
3.1, get method (parameters: url address, scope, successful callback, failure callback); after the application layer calls the Http manager to initiate a request, the data of the request can be taken in the success/failure callback and immediately updated to the application layer;
3.2, post method (parameters: url address, data, scope, successful callback, failure callback); after the application layer calls the manager to initiate a request, the data of the request can be taken in the success/failure callback and immediately updated to the application layer;
3.3 http destroy remove (parameter: request sequence id).
II, HTTP/HTTPS communication data updating process:
s1: creating an Http request result processor and an Http manager;
the step is realized by the first-stage creation and the early-stage creation.
S2: an application layer of the client calls an Http manager to initiate an Http request to the server;
s3: and the Http manager creates a corresponding Http class according to the initiated Http request, and initiates the Http request to the server according to the Http class. The Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager;
specifically, the step is realized by the first-stage creation.
S4: and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer.
In a particular embodiment of the method of the present invention,
before the step S4, the method of this embodiment further includes:
s04: creating an Http request result processor, wherein an abstract and general Http request result callback function and a scope are built in the Http request result processor.
Specifically, the step is realized by the first-stage creation.
The step S4 specifically includes the following sub-steps:
s41: the Http request result processor acquires a request result of the Http request from the server according to a built-in general Http request result callback function, and sends the request result to the Http class of the Http manager;
s42: if the request result corresponds to the request successfully, the Http class constructs a Http request successful processor corresponding to the Http request, and because the Http request successful processor corresponding to the request successfully here, a request result callback function included in the Http request successful processor is a request successful callback function;
if the request result corresponds to a request failure, the Http class constructs a Http request failure processor corresponding to the Http request, wherein the Http request failure processor comprises a request failure callback function;
s43: when the request result corresponds to the request success, the Http manager executes a callback function of the Http request success processor; and when the request result corresponds to the request failure, executing a request failure callback function in the Http request failure processor, and then sending the corresponding request result to an application layer through the request success callback function or the request failure callback function.
More specifically, two specific request methods for Http request are as follows: according to the get request method and the post request method, an application layer only needs to call the get method and the post method in the Http manager in a unified mode to transfer a url address, data (the get mode can be ignored), a scope, a success callback and a failure callback, and a request result can return and update data through the success/failure callback.
If the built-in request method in the Http class is a get method, that is, the client initiates the Http request by the get method, the request result received by the Http class corresponds to the parameter of the get request method, that is, the request result returns data according to the parameter in the get request method.
If the request method built in the Http class is a post method, that is, the client initiates the Http request by a get method, the request result received by the Http class corresponds to a parameter of the post request method;
and the Http class constructs the Http request success handler or the Http request failure handler according to the scope recorded in the received request result and the request success callback or the request failure callback parameter.
Preferably, the method of this embodiment further includes an Http request destroy removal process:
s5: and removing the sequence id of an Http request in the Http request queue through the Http manager, namely destroying the monitoring and updating of the Http request corresponding to the sequence id.
Example two
In this embodiment, on the basis of the first embodiment, the interaction process of the server-side data change automation update instance based on the Http request, which is described in fig. 2, is further defined:
wherein, (1) http rodler: the Http result processor comprises a Http request callback function callback and a callback scope context which are abstract and general parameters;
(2) http-success handler: a result processor for which Http request is successful;
(3) Http-errorHandler: a result handler that fails the Http request;
(3) http-get is the get request mode of the communication layer Http;
(4) http-post: a post request mode of a communication layer Http;
(5) HttpRequestManager-get: an application layer, an Http manager get request mode, and a result processor for success and failure of Http request is constructed through a second parameter, a third parameter and a fourth parameter, wherein the first parameter is a request address, the second parameter is a processing scope (including a success callback scope and a failure callback scope) of Http request result, the third parameter is a callback function for success request, and the fourth parameter is a callback function for failure request;
(6) HttpRequestManager-post: the application layer, the Http manager post request mode, constructs a Http request success and failure result processor through the third, fourth and fifth parameters, the first parameter is a request address, the second parameter is data to be transmitted, the third parameter is a Http request result processing scope (including a success callback scope and a failure callback scope), the fourth parameter is a callback function of success request, and the fifth parameter is a callback function of failure request.
EXAMPLE III
This embodiment corresponds to the first and second embodiments, and provides a specific application scenario:
h5 client Http initiates a login request, and the server needs to return user data, then:
initiating a get request through an HttpRequestManager, and simultaneously transmitting a callback scope after the request, a callback function with a successful request and a callback function with a failed request; when a get request is initiated, an Http request class is packaged, and a processor for success of the Http request and failure of the Http request is created for the request; after the result is received, the callback function which is transmitted in the application layer and has a successful request or the callback function which has a failed request can be executed according to the success or failure of the result, and the success and the failure can acquire the login message data of the server from the callback function.
Example four
Corresponding to the first to third embodiments, the present embodiment provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when being executed by a processor, can implement the steps included in the method for automatically updating data of H5 across engine clients according to any one of the first to third embodiments, and specific contents of the steps are not repeated here, and refer to the records of the first embodiment, the second embodiment, or the third embodiment in detail.
It should be understood by those skilled in the art that all or part of the processes in the above technical solutions may be implemented by instructing the related hardware through a computer program, where the program may be stored in a computer-readable storage medium, and when executed, the program may include the processes of the above methods.
The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
In summary, the method and the storage medium for automatically updating H5 cross-engine client data provided by the invention can not only realize monitoring of server data of HTTP/HTTPs short link communication and automatic updating of data change; and the operation process is greatly simplified, and meanwhile, the data distribution and maintenance cost is reduced.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (7)
- A method for H5 cross-engine client data automation update, comprising:an application layer of the client calls an Http manager to initiate an Http request to the server;the Http manager creates a corresponding Http class according to the Http request, and initiates the Http request to a server according to the Http class, wherein the Http class is internally provided with the Http request and a request result callback function, and the request result callback function is bound with the Http manager;and the Http manager acquires the request result of the Http request from the server according to the request result callback function, and returns the request result to the application layer.
- 2. The method for H5 cross-engine client data automation updating according to claim 1, wherein the Http manager is built-in with Http request queue, the Http request queue stores with the sequence id of Http request as key value and Http class corresponding to Http request as value;the Http class is also embedded with a sequence id of the Http request.
- 3. The method of H5 cross-engine client data automation updating of claim 1 wherein the request result callback functions include a request successful callback function and a request failed callback function;the method further comprises the following steps:creating an Http request result processor, wherein an abstract and general Http request result callback function and a scope are built in the Http request result processor;the Http manager obtains a request result of the Http request from a server according to the request result callback function, and returns the request result to an application layer, specifically:the Http request result processor acquires a request result of the Http request from the server according to a general Http request result callback function, and sends the request result of the Http request to the Http class of the Http manager;if the request result corresponds to the request success, the Http class constructs a Http request success handler corresponding to the Http request, and the Http request success handler includes the request success callback function;if the request result corresponds to a request failure, the Http class constructs a Http request failure processor corresponding to the Http request, wherein the Http request failure processor comprises the request failure callback function;and the Http manager executes a request success callback function in the Http request success processor or a request failure callback function in the Http request failure processor, and sends the request result to the application layer through the request success callback function or the request failure callback function.
- 4. The method of H5 cross-engine client data automation updating of claim 3, wherein the Http manager has built in request methods including a get request method and a post request method; the parameters of the get request method comprise a url address, a scope, a request success callback function and a request failure callback function; the parameters of the post request method comprise a url address, data, a scope, a request success callback function and a request failure callback function;the Http class is also internally provided with a scope of the request result callback function and a request method for calling the Http request by an application layer;when an application layer calls a get request method in an Http manager to send an Http request to a server, a built-in request method in the Http class is a get method, and the request result callback function includes a request success callback function and a request failure callback function of the get request method;when an application layer calls a post request method in an Http manager to send an Http request to a server, a request method built in the Http class is a post method, and the request result callback function includes a request success callback function or a request failure callback function of the get request method.
- 5. The method for H5 cross-engine client data automation updating of claim 4,if the built-in request method in the Http class is a get method, the request result received by the Http class corresponds to a parameter of the get request method;if the request method built in the Http class is a post method, the request result received by the Http class corresponds to a parameter of the post request method;and the Http class constructs and obtains the Http request success handler or the Http request failure handler according to the scope recorded in the received request result and the request success callback or the request failure callback parameter.
- 6. The method for H5 cross-engine client data automation updating of claim 2, further comprising:the sequence id of an Http request in the Http request queue is removed by the Http manager.
- 7. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, is adapted to carry out the steps of the method for automated update of H5 cross-engine client data according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910109573.0A CN111552488B (en) | 2019-02-11 | 2019-02-11 | Method and storage medium for H5 cross-engine client data automation updating |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910109573.0A CN111552488B (en) | 2019-02-11 | 2019-02-11 | Method and storage medium for H5 cross-engine client data automation updating |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552488A true CN111552488A (en) | 2020-08-18 |
| CN111552488B CN111552488B (en) | 2022-07-05 |
Family
ID=72003692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910109573.0A Active CN111552488B (en) | 2019-02-11 | 2019-02-11 | Method and storage medium for H5 cross-engine client data automation updating |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552488B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101138219A (en) * | 2005-03-10 | 2008-03-05 | 国际商业机器公司 | Application of communication method between client computer |
| CN104253788A (en) * | 2013-06-26 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Data processing method and system, client, and page engine |
| US8954989B1 (en) * | 2007-11-19 | 2015-02-10 | Appcelerator, Inc. | Flexible, event-driven JavaScript server architecture |
| CN109040072A (en) * | 2018-08-06 | 2018-12-18 | 武汉斗鱼网络科技有限公司 | A kind of method, system, server and the storage medium of client authorization log-on webpage |
| CN109254854A (en) * | 2018-08-15 | 2019-01-22 | 中国平安人寿保险股份有限公司 | Asynchronous invoking method, computer installation and storage medium |
-
2019
- 2019-02-11 CN CN201910109573.0A patent/CN111552488B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101138219A (en) * | 2005-03-10 | 2008-03-05 | 国际商业机器公司 | Application of communication method between client computer |
| US8954989B1 (en) * | 2007-11-19 | 2015-02-10 | Appcelerator, Inc. | Flexible, event-driven JavaScript server architecture |
| CN104253788A (en) * | 2013-06-26 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Data processing method and system, client, and page engine |
| CN109040072A (en) * | 2018-08-06 | 2018-12-18 | 武汉斗鱼网络科技有限公司 | A kind of method, system, server and the storage medium of client authorization log-on webpage |
| CN109254854A (en) * | 2018-08-15 | 2019-01-22 | 中国平安人寿保险股份有限公司 | Asynchronous invoking method, computer installation and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 白林如: "《ASP.NET底层处理机制HttpModule和HttpHandler的应用》", 《计算机与数字工程》 * |
| 谢仕义: "《嵌入式Web服务器的设计及其CGI实现》", 《计算机工程与设计》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552488B (en) | 2022-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7813336B2 (en) | Service providing system cooperative with VoIP and web environments and a method therefor | |
| US8848893B2 (en) | Method and apparatus for callback processing in telecommunication capability opening | |
| US7979519B2 (en) | System for providing information between different protocol environments cooperative with each other and a method therefor | |
| US8713365B2 (en) | Re-establishing push notification channels via user identifiers | |
| CN108712485B (en) | Resource subscription method and device for Internet of things equipment | |
| US9219774B2 (en) | Exchange of callback information | |
| EP2669803A2 (en) | Unifying programming models in connectivity framework | |
| CN115426391A (en) | Remote procedure call protocol self-adaption method, related device and server | |
| CN107517227B (en) | Session implementation method and device for distributed consistency system | |
| CN111611091A (en) | Service calling method, device and medium for business object | |
| CN108347445A (en) | Realize the method and device of far call | |
| US11379446B1 (en) | Session-based data storage for chat-based communication sessions | |
| CN111552901B (en) | H5 cross-engine client data automation updating method and storage medium | |
| CN113556359A (en) | Communication protocol conversion method, device, system and gateway device | |
| CN111552488B (en) | Method and storage medium for H5 cross-engine client data automation updating | |
| CN112217845B (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN108334322B (en) | Data request method and system of MVC framework | |
| CN115134422A (en) | Service processing method, video network terminal, master control device, electronic device and medium | |
| US20210243585A1 (en) | System and method for implementing a softphone emergency dialing architecture | |
| CN109408248B (en) | Inter-thread communication system under Linux | |
| CN110008032B (en) | Communication mode realization method and electronic equipment | |
| US11949648B1 (en) | Remote connectivity manager | |
| CN111371823A (en) | Method for client to access micro-service in non-WEB scene | |
| CN115102854B (en) | Remote procedure call route management control method, system and equipment for micro-service | |
| CN111917808B (en) | Load control method, service provider NF and service user NF |
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 |