CN114844875A - Application Programming Interface (API) management method, device, equipment and medium - Google Patents

Application Programming Interface (API) management method, device, equipment and medium Download PDF

Info

Publication number
CN114844875A
CN114844875A CN202210422967.3A CN202210422967A CN114844875A CN 114844875 A CN114844875 A CN 114844875A CN 202210422967 A CN202210422967 A CN 202210422967A CN 114844875 A CN114844875 A CN 114844875A
Authority
CN
China
Prior art keywords
api
module
file
network request
interface
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
Application number
CN202210422967.3A
Other languages
Chinese (zh)
Other versions
CN114844875B (en
Inventor
陈�胜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Yishi Huolala Technology Co Ltd
Original Assignee
Shenzhen Yishi Huolala Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Yishi Huolala Technology Co Ltd filed Critical Shenzhen Yishi Huolala Technology Co Ltd
Priority to CN202210422967.3A priority Critical patent/CN114844875B/en
Publication of CN114844875A publication Critical patent/CN114844875A/en
Application granted granted Critical
Publication of CN114844875B publication Critical patent/CN114844875B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses an Application Programming Interface (API) management method, device, equipment and medium. The API management method comprises the steps of constructing an API parent file which can be used for network requests; performing module differentiation and classification according to project scenes, and establishing module API files according to modules; receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request. The invention differentiates and classifies modules according to project scenes, establishes module API files according to the modules, and equivalently disassembles the APIs according to the project scenes instead of aggregating all the APIs together. Due to the classification, the total amount of writing required by the service implementation party by the network layer is reduced, and the workload is reduced overall.

Description

Application Programming Interface (API) management method, device, equipment and medium
Technical Field
The invention relates to the technical field of internet, in particular to an Application Programming Interface (API) management method, device, equipment and medium.
Background
With the rapid development of mobile internet, internet of things and big data of all things interconnection are in great tendency, and almost no APP with functions not based on networking exists, so the importance of network requests in the development of mobile terminal APP is self-evident. Data acquisition and data uploading of the APP are not separated from network connection, and each data pulling or uploading and downloading needs to be realized by initiating an API request, so that the API requests become an important task in APP development after being managed.
The packaging of network requests in the market at present mainly comprises intensive and discrete APIs
1. Intensive API
Introduction: all API calls only have one class, then the class receives API names, API parameters and call-back landing points, namely, each request in a project can go through a uniform entry, a URL and Param of the request and a request mode are exposed to the outside, the entry is generally realized through a single-case or class method, and the official demo of AFNet encapsulates network requests in an intensive mode, namely, the current popular network request mode.
2. Discrete API
Introduction: the discrete API calls are such that one API corresponds to one APIManager, which then takes off only by providing parameters, the API name, and the landing method are already integrated into the APIManager. That is, each network request class is an object, and its URL and neither the request mode nor the response mode are exposed to external calls. The network request mode can be only specified by a mode of overloading or realizing a protocol internally, only Param needs to be transmitted for external calling, and YTKNetwork is the network request mode adopted.
A disadvantage of the intensive API management approach is that the customization for each request is not strong enough. The disadvantages of the discrete API management mode are: the network layer needs a service implementation party to write, and phase change increases part of workload. Thus, there is a need for alternative API management approaches.
Disclosure of Invention
Aiming at the reasons that the intensive API and the discrete API management mode in the prior art have defects, the invention provides the following technical scheme.
The invention adopts a technical scheme that:
an Application Programming Interface (API) management method, comprising:
constructing an API (application programming interface) parent file, wherein the API parent file can be used for network requests;
performing module differentiation and classification according to project scenes, and establishing module API files according to modules;
receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
Optionally, the constructing the API parent file specifically includes:
writing a public function for the API parent file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, and the APP uploads the data and downloads the data from the server.
Optionally, each module API file accommodates a network request interface of the module, and can call a public function of the API parent file to perform a network request.
Optionally, the interface is configured to call the API parent file to perform a network request, and specifically includes:
the interface is used for calling the public function of the API parent file to carry out network request.
Optionally, the performing module differentiation classification according to the project scenario, and the establishing a module API file according to the module specifically includes:
and performing module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the services of the projects, wherein the module API files comprise different subclasses.
Optionally, the exposed function is performed in a parent high-level language application programming interface.
The other technical scheme adopted by the invention is as follows: an Application Programming Interface (API) request method, comprising:
initiating a network request;
matching a corresponding module API file according to the project scene of the network request, and calling an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request;
and receiving target data returned based on the network request, and returning the target data to the application program.
The other technical scheme adopted by the invention is as follows: an Application Programming Interface (API) management apparatus, comprising:
the building module is used for building an API (application program interface) parent file, and the API parent file can be used for network requests;
the classification and establishment module is used for performing module differentiation and classification according to project scenes and establishing a module API file according to the module;
the receiving and opening module is used for receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
The other technical scheme adopted by the invention is as follows: an Application Programming Interface (API) management device,
the method comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the API management method as described above when executing the computer program.
The other technical scheme adopted by the invention is as follows: computer-readable storage medium having stored therein program data for implementing the method as described above when executed by a processor.
The invention has the beneficial effects that: different from the situation of the prior art, the API management method of the application programming interface comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; performing module differentiation and classification according to project scenes, and establishing module API files according to modules; receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request. The invention differentiates and classifies modules according to project scenes, establishes the module API files according to the modules, equivalently disassembles the APIs according to the project scenes instead of aggregating all the APIs together, and has lower coupling degree. Due to the classification, the total amount of writing required by the service implementation party by the network layer is reduced, and the workload is reduced overall. And the parent class is set to close in the request, namely, the network request is not carried out on each subclass, but the network request method is put into the parent class to be executed, so that the customization of the classification level is realized, the customization is enhanced on the whole, and the polymerization degree is higher.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. Wherein:
FIG. 1 is a flowchart of one embodiment of an API management method provided by the present invention;
FIG. 2 is a flowchart of one embodiment of an API request method provided by the present invention;
FIG. 3 is a block diagram of an API management device according to the present invention;
FIG. 4 is a block diagram of an API management device according to the present invention;
FIG. 5 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It is further noted that, for the sake of convenience, the drawings show only some, but not all, of the methods and processes associated with the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "comprising" and "having," as well as any variations thereof, in the present invention are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In software engineering, high-cohesion low-coupling is a standard for judging whether code design is good or bad, and specifically, when an object-oriented program is designed, whether the cohesion of a class is high or not and whether the coupling degree is low or not are judged. The aim is to greatly enhance the reusability and portability of the module. Generally, the higher the degree of cohesion of the modules in the program structure, the lower the degree of coupling between the modules. Cohesion is a measure of the connections within a module from a functional perspective, and a good cohesive module should do exactly one thing. Coupling is a measure of the interconnection between modules in a software structure, and the strength of coupling depends on the complexity of the interface between the modules, the point of entry or access to a module, and the data passing through the interface.
In addition to high cohesion and low coupling, in software engineering, a concept of parent and child classes is provided, that is, two classes (files) are in a relationship between a parent and a child, and the child classes can inherit functions (public methods) of the parent class.
According to the code structure mode with high cohesion and low coupling, the existing mainstream API management mode in the market is combined, the advantages are raised, the shortcomings are overcome, decoupling is carried out through business classification and father-son design (the decoupling is carried out to sub-classes such as AApis, BApis and CApis), a mode of realizing high cohesion is carried out when a network request is obtained and closing is carried out (the functional method disclosed by father APIManager is realized by sub-classes such as AApis, BApis and CApis), and therefore the structure of high cohesion and low coupling of an API code is realized.
As shown in fig. 1, an embodiment of the present invention provides an application programming interface API management method, including:
step 10, constructing an API (application programming interface) parent file, wherein the API parent file can be used for network requests;
step 20, performing module differentiation and classification according to project scenes, and establishing module API files according to modules;
step 30, receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
The invention has the beneficial effects that: different from the situation of the prior art, the API management method of the application programming interface comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; performing module differentiation and classification according to project scenes, and establishing module API files according to modules; receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request. The invention differentiates and classifies modules according to project scenes, establishes the module API files according to the modules, equivalently disassembles the APIs according to the project scenes instead of aggregating all the APIs together, and has lower coupling degree. Due to the classification, the total amount of writing required by the service implementation party by the network layer is reduced, and the workload is reduced overall. And the parent class is set to close up when in request, namely, the network request is not carried out on each child class, but the network request method is put into the parent class to be executed, so that the customization of the classification level is realized, the customization is enhanced on the whole, and the polymerization degree is higher.
Further, the constructing the API parent file specifically includes:
writing a public function for the API parent file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, and the APP uploads the data and downloads the data from the server.
Specifically, firstly, an API parent file (API manager) is compiled with public functions (functions required by subclasses such as AApis, BApis and cappis) and integrated with a series of public functions, such as data pulling (data request from APP to server), data reporting (data upload from APP to server), APP downloading and other public function packages, without relating to specific service logic;
furthermore, each module API file receives a network request interface of the module and can call the public function of the API parent file to carry out network request.
Further, the module differentiation and classification according to the project scenario, and the module API file establishment according to the module specifically includes:
and performing module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the services of the projects, wherein the module API files comprise different subclasses.
Specifically, the items are differentiated and classified, and according to different item scenes, each module establishes an API management class (AApis, BApis, capis.) which is a module API file, each API management class only stores a network request interface of the module, and only calls a method provided by a parent class to perform a network request, without processing specific request logic and data logic.
Further, the interface is configured to call the API parent file to perform a network request, and specifically includes:
the interface is used for calling the public function of the API parent file to carry out network request.
In the specific service code writing process, when the project scene of the network request is related, the API writing is directly carried out in the API management class (i.e. the corresponding module API file, such as BApis) of the corresponding module
For example: the order data is pulled in the B module, a network request is needed, and at the moment, an interface- (void) getOrderDataFromServer for pulling the order data is opened in a BApis class;
the specific implementation of the interface is to call a method in the parent APIManager to perform a network request.
The key point of the invention is that the API is disassembled for the service modules of different project scenes, and module API files are established according to the modules, namely, the modules are divided into subclasses such as AApis, BApis, CApis and the like according to the services of the projects, rather than aggregating all the APIs together, namely, low coupling;
moreover, an API parent file is set to be closed when in request, namely, network requests are not carried out on each subclass, but a public function (open function) method is put into a parent high-level language application programming interface (HLLAPIManager) to be executed, so that high cohesion is achieved;
in the process of writing a specific service code, subclasses such as AApis, BApis and CApis of the service code of a required network do not relate to specific network request logic, and network request codes of a parent class HLLAPIManager do not relate to specific service logic;
when different service modules are developed, the specific request mode of the API parent file is not needed to be known, only the interface of the API parent file is needed to be called to carry out network request, the management of the API interface is only carried out in the API file of the module, no specific network request is carried out, the classification of the API is distinguished according to the module, a Manager file is not needed to be arranged in one API, and the API of the same module is arranged in a subclass, so that intensive arrangement in the same class can be avoided, a large number of class files are not needed to be generated like a discrete type, the clear service logic and technical logic of a high-cohesion low-coupling design mode in software engineering are met, and the respective defects of intensive API management and discrete API management modes in the prior art are overcome.
The embodiment of the invention mainly solves the pain of API management mode in the prior art in iOS app development, and optimizes the experience of a developer by optimizing a code structure, thereby improving the development efficiency and code robustness, and enabling the code to have more expansibility and a clearer code logic structure.
As shown in fig. 2, an embodiment of the present invention further provides an application programming interface API requesting method, including:
step 60, initiating a network request;
step 70, matching a corresponding module API file according to the project scene of the network request, and calling an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request;
and 80, receiving target data returned based on the network request, and returning the target data to the application program.
It should be noted that the API request method is performed based on the API management method of the foregoing embodiment, and is a method for implementing a process of initiating a network request and returning template data to a network request initiating end. The API requesting method of the present embodiment and the API managing method of the foregoing embodiment are based on the same inventive concept, and the specific implementation process thereof is detailed in the method embodiment, and the technical features in the foregoing embodiments are all applicable in the present embodiment, and are not described in detail herein.
According to the above embodiment, as shown in fig. 3, an application programming interface API management apparatus 50 is further provided in an embodiment of the present invention, where the application programming interface API management apparatus 50 includes:
a building module 51, configured to build an API parent file, where the API parent file may be used for a network request;
a classification and creation module 52 for performing module differentiation and classification according to the project scenario, and creating a module API file according to the module;
a receiving and opening module 53, configured to receive a network request, match a corresponding module API file according to a project scenario of the network request, and open an interface of the project scenario in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
The API management apparatus of the present embodiment and the API management method of the foregoing embodiment are based on the same inventive concept, and specific implementation processes thereof are detailed in the method embodiments, and technical features of the API management method embodiments are correspondingly applicable in the present embodiment, which is not described in detail herein.
As shown in fig. 4, an embodiment of the present invention further provides an application programming interface API management apparatus 100.
The API management device 100 includes a processor 110 and a memory 120. Wherein the processor 110 and the memory 120 are coupled. The memory 120 stores therein a computer program for executing the above application programming interface API management method.
The application programming interface API management apparatus 100 includes:
a memory 120 for storing a computer program;
the processor 110 is configured to implement the steps of the API management method as described above when executing the computer program.
The API management device of the present embodiment and the API management method of the foregoing embodiment are based on the same inventive concept, and specific implementation processes thereof are detailed in the method embodiments, and technical features in the API management method embodiments are correspondingly applicable in the present embodiment, which is not described in detail herein.
Referring to fig. 5 in particular, fig. 5 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present invention.
Program data 210 is included in computer-readable storage medium 200. Program data 210, when executed by a processor, may implement the application programming interface API management methods described above.
In contrast to the prior art, the present invention provides an application programming interface, API, management method.
The invention has the beneficial effects that: different from the situation of the prior art, the invention provides an Application Programming Interface (API) management method, which comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; performing module differentiation and classification according to project scenes, and establishing module API files according to modules; receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request. The invention differentiates and classifies modules according to project scenes, establishes the module API files according to the modules, equivalently disassembles the APIs according to the project scenes instead of aggregating all the APIs together, and has lower coupling degree. Due to the classification, the total amount of writing required by the service implementation party by the network layer is reduced, and the workload is reduced overall. And the parent class is set to close in the request, namely, the network request is not carried out on each subclass, but the network request method is put into the parent class to be executed, so that the customization of the classification level is realized, the customization is enhanced on the whole, and the polymerization degree is higher.
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 performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. An API management method, comprising:
constructing an API (application programming interface) parent file, wherein the API parent file can be used for network requests;
performing module differentiation and classification according to project scenes, and establishing module API files according to modules;
receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
2. The method of claim 1, wherein the constructing the API parent class file specifically comprises:
writing a public function for the API parent file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, and the APP uploads the data and downloads the data from the server.
3. The method of claim 2, wherein each module API file houses a network request interface of the module and is capable of invoking a publish function of the API parent file for network requests.
4. The method of claim 3, wherein the interface is configured to call the API parent file to make a network request specifically includes:
the interface is used for calling the public function of the API parent file to carry out network request.
5. The method according to claim 4, wherein said performing module differentiation classification by project scenario, and building module API files by module specifically comprises:
and performing module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the services of the projects, wherein the module API files comprise different subclasses.
6. The method of claim 5, wherein the exposed function is performed in a parent high-level language application programming interface.
7. An API request method, comprising:
initiating a network request;
matching a corresponding module API file according to the project scene of the network request, and calling an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request;
and receiving target data returned based on the network request, and returning the target data to the application program.
8. An Application Programming Interface (API) management apparatus, comprising:
the building module is used for building an API (application program interface) parent file, and the API parent file can be used for network requests;
the classification and establishment module is used for performing module differentiation and classification according to project scenes and establishing a module API file according to the module;
the receiving and opening module is used for receiving a network request requirement, matching a corresponding module API file according to a project scene of the network request requirement, and opening an interface of the project scene in the corresponding module API file; the interface is used for calling the API parent file to carry out network request.
9. An Application Programming Interface (API) management device,
the method comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the application programming interface, API, management method according to any one of claims 1 to 6 when executing said computer program.
10. A computer-readable storage medium, in which program data are stored which, when being executed by a processor, are adapted to carry out the method of any one of claims 1-6.
CN202210422967.3A 2022-04-21 2022-04-21 Application programming interface API management method, device, equipment and medium Active CN114844875B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210422967.3A CN114844875B (en) 2022-04-21 2022-04-21 Application programming interface API management method, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210422967.3A CN114844875B (en) 2022-04-21 2022-04-21 Application programming interface API management method, device, equipment and medium

Publications (2)

Publication Number Publication Date
CN114844875A true CN114844875A (en) 2022-08-02
CN114844875B CN114844875B (en) 2024-02-06

Family

ID=82566598

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210422967.3A Active CN114844875B (en) 2022-04-21 2022-04-21 Application programming interface API management method, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN114844875B (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060020950A1 (en) * 2004-06-30 2006-01-26 Patrick Ladd Apparatus and methods for implementation of network software interfaces
KR20110016124A (en) * 2009-08-11 2011-02-17 (주)시스포유아이앤씨 Web contents managenment method in moduled web-client application framework using xml
US20110251925A1 (en) * 2010-04-09 2011-10-13 The Knot, Inc. Systems and methods for a centralized gift registry with automatic retailer-specific registry creation
CN102622229A (en) * 2012-02-24 2012-08-01 北京星网锐捷网络技术有限公司 Fusion method, fusion system and fusion device of development frameworks of different types
US20140089383A1 (en) * 2012-09-27 2014-03-27 National Taiwan University Method and system for automatic detecting and resolving apis
CN108769249A (en) * 2018-06-20 2018-11-06 武汉斗鱼网络科技有限公司 The high extended network framework and implementation method of iOS high-performance, server and medium
CN110659017A (en) * 2019-09-19 2020-01-07 上海客佳信息科技有限公司 External request processing method and related device
CN111949337A (en) * 2020-08-07 2020-11-17 中国建设银行股份有限公司 Accounting processing method, device, terminal and storage medium
CN112272218A (en) * 2020-10-16 2021-01-26 苏州浪潮智能科技有限公司 Cloud platform instance resource operation method and device, computer equipment and storage medium
CN112346774A (en) * 2019-08-06 2021-02-09 北京京东尚科信息技术有限公司 Method and device for generating application installation package
CN112748908A (en) * 2020-12-31 2021-05-04 广东广宇科技发展有限公司 Restful service development method and device based on SSM framework
CN112800120A (en) * 2021-01-26 2021-05-14 政采云有限公司 Service processing method and device
CN114371858A (en) * 2021-12-13 2022-04-19 天翼物联科技有限公司 Code processing system, method, device and storage medium based on application component

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060020950A1 (en) * 2004-06-30 2006-01-26 Patrick Ladd Apparatus and methods for implementation of network software interfaces
KR20110016124A (en) * 2009-08-11 2011-02-17 (주)시스포유아이앤씨 Web contents managenment method in moduled web-client application framework using xml
US20110251925A1 (en) * 2010-04-09 2011-10-13 The Knot, Inc. Systems and methods for a centralized gift registry with automatic retailer-specific registry creation
CN102622229A (en) * 2012-02-24 2012-08-01 北京星网锐捷网络技术有限公司 Fusion method, fusion system and fusion device of development frameworks of different types
US20140089383A1 (en) * 2012-09-27 2014-03-27 National Taiwan University Method and system for automatic detecting and resolving apis
CN108769249A (en) * 2018-06-20 2018-11-06 武汉斗鱼网络科技有限公司 The high extended network framework and implementation method of iOS high-performance, server and medium
CN112346774A (en) * 2019-08-06 2021-02-09 北京京东尚科信息技术有限公司 Method and device for generating application installation package
CN110659017A (en) * 2019-09-19 2020-01-07 上海客佳信息科技有限公司 External request processing method and related device
CN111949337A (en) * 2020-08-07 2020-11-17 中国建设银行股份有限公司 Accounting processing method, device, terminal and storage medium
CN112272218A (en) * 2020-10-16 2021-01-26 苏州浪潮智能科技有限公司 Cloud platform instance resource operation method and device, computer equipment and storage medium
CN112748908A (en) * 2020-12-31 2021-05-04 广东广宇科技发展有限公司 Restful service development method and device based on SSM framework
CN112800120A (en) * 2021-01-26 2021-05-14 政采云有限公司 Service processing method and device
CN114371858A (en) * 2021-12-13 2022-04-19 天翼物联科技有限公司 Code processing system, method, device and storage medium based on application component

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
AUGENSTERN-MONTH: "Http调用第三方接口的两种方式实例", CSDN *
樊翠等: "基于D3D的三维游戏引擎的设计与实现", 科学技术与工程 *

Also Published As

Publication number Publication date
CN114844875B (en) 2024-02-06

Similar Documents

Publication Publication Date Title
KR100453824B1 (en) XML based network management system and method for configuration management of heterogeneous network devices
EP2418825A1 (en) Method and system for generating open telecommunication service based on internet
JP2007511018A (en) Method and apparatus for composing software
CN105959302B (en) A kind of terminal management system and method
WO2011060735A1 (en) Method,device and system for invoking widget
CN102209111A (en) Open cross-platform system for cloud computing mobile network terminal equipment
CN108696523B (en) Response method and device for call service
KR100670605B1 (en) System and method for servicing multimedia contents and recording medium thereof
CN114024821A (en) Northbound interface management method and device
CN112698930B (en) Method, device, equipment and medium for obtaining server identification
CN113296744A (en) Application development system and method
CN109683992B (en) Method and apparatus for managing objects
CN114844875B (en) Application programming interface API management method, device, equipment and medium
US8806512B2 (en) Collocation in a Java virtual machine of JSLEE, SIP servlets, and Java EE
EP2445171A1 (en) File transfer protocol client and implementing method thereof
CN113296987B (en) Interface calling method and device for calling module, computer equipment and storage medium
CN111104122A (en) Method for mapping xml service logic to java service logic
CN113347609B (en) Wireless intelligent control platform
WO2010048815A1 (en) Method and system for developing and installing network management features of services
CN112905273A (en) Service calling method and device
CN113810448A (en) Cloud service method, deployment method, device, electronic equipment and storage medium
CN112181401A (en) Application construction method and application construction platform
TWI838107B (en) A network function virtualization orchestrator system, method and computer-readable medium thereof based on mobile network slicing function
CN112988125B (en) Data bridging method, device, equipment and storage medium
CN117076160B (en) Component calling method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant