CN114844875B - Application programming interface API management method, device, equipment and medium - Google Patents
Application programming interface API management method, device, equipment and medium Download PDFInfo
- Publication number
- CN114844875B CN114844875B CN202210422967.3A CN202210422967A CN114844875B CN 114844875 B CN114844875 B CN 114844875B CN 202210422967 A CN202210422967 A CN 202210422967A CN 114844875 B CN114844875 B CN 114844875B
- Authority
- CN
- China
- Prior art keywords
- api
- module
- file
- network request
- project
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 48
- 238000000034 method Methods 0.000 claims abstract description 49
- 230000004069 differentiation Effects 0.000 claims abstract description 21
- 230000006870 function Effects 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 238000010276 construction Methods 0.000 claims description 3
- 239000008186 active pharmaceutical agent Substances 0.000 abstract description 10
- 238000010168 coupling process Methods 0.000 description 12
- 238000005859 coupling reaction Methods 0.000 description 12
- 230000008878 coupling Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 241001368098 Capis Species 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
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. An Application Programming Interface (API) management method comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules; receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, 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. According to the method, module differentiation and classification are carried out according to project scenes, module API files are established according to the modules, and the method is equivalent to disassembling the APIs of the modules according to the project scenes, rather than gathering all APIs together. For classification reasons, the total amount of traffic effectuators required to write by the network layer is reduced, reducing the effort as a whole.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a medium for managing an API.
Background
With the rapid development of the mobile internet, the internet of things and big data of the internet of things are all tendency, and there are few' functions of the APP based on the internet, so the importance of network requests in the development of the APP at the mobile terminal is self-evident. The data acquisition and the data uploading of the APP are not connected with the network, and each time of data pulling or uploading and downloading is realized by initiating an API request, so that the management of the API requests becomes an important task in the development of the APP.
The packages for network requests currently on the market are mainly intensive and discrete APIs
1. Intensive API
Introduction: the calling of all APIs has only one class, and then the class receives the name of the API, the parameters of the API and callback landing points, namely, each request in the project can go through a unified entry, the URL and Param of the request and the request mode are exposed to the outside, the entry is generally realized by a single instance or class method, the official demo of AFNetworking is the encapsulation of the network request in an intensive mode, and the method is a popular network request mode at present.
2. Discrete API
Introduction: the discrete API call is such that one API corresponds to one apimanagement, which then only needs to provide parameters to run, and the API name, landing mode, have been integrated into the apimanagement. I.e., each network request class is an object whose URL, as well as the request and response means, is not exposed to external calls. Only the specification can be carried out internally by means of reloading or realizing a protocol, and only Param needs to be transmitted to external call, and YTKNETWork is the network request mode.
The 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 approach are: the network layer needs the service realization party to write, and part of workload is increased by phase change. Thus, there is a need for alternative ways of API management.
Disclosure of Invention
Aiming at the reasons that the intensive API and the discrete API management mode have defects in the prior art, 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 parent class file, wherein the API parent class file can be used for network requests;
carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules;
and receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, and opening an interface of the project scene in the corresponding module API file, wherein the interface is used for calling the API parent file to carry out the network request.
Optionally, the constructing the API parent file specifically includes:
writing the public function of the API parent class file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, the APP uploads data to the server and the APP downloads data.
Optionally, each module API file stores a network request interface of the module, and can call a public function of the API parent file to make a network request.
Optionally, the interface is configured to call the API parent file to perform a network request specifically includes:
the interface is used for calling the public function of the API parent file to carry out network request.
Optionally, the module differentiation classification is performed according to project scenes, and the module API file establishment according to the modules specifically includes:
and carrying out module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the project, wherein the module API files comprise different subclasses.
Optionally, the disclosed functionality is performed in a parent high-level language application programming interface.
The invention adopts another technical scheme that: an application programming interface API requesting method, comprising:
initiating a network request;
matching corresponding module API files according to the project scene of the network request, and calling interfaces of the project scene in the corresponding module API files, wherein the interfaces are used for calling API parent class files to perform the network request;
and receiving target data returned based on the network request, and returning the target data to the application program.
The invention adopts another technical scheme that: an application programming interface API management device comprising:
the construction module is used for constructing an API parent class file which can be used for network requests;
the classification and establishment module is used for carrying out module differentiation classification according to project scenes and establishing module API files according to the modules;
the receiving and opening module is used for receiving network request demands, matching corresponding module API files according to project scenes of the network request demands, opening interfaces of the project scenes in the corresponding module API files, and calling the API parent class files to carry out network requests.
The invention adopts another technical scheme that: an API management device for an application programming interface,
comprising the following steps:
a memory for storing a computer program;
and the processor is used for realizing the steps of the application programming interface API management method when executing the computer program.
The invention adopts another technical scheme that: a computer readable storage medium having stored therein program data for implementing a method as described above when executed by a processor.
The beneficial effects of the invention are as follows: different from the prior art, the Application Programming Interface (API) management method provided by the invention comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules; and receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, and opening an interface of the project scene in the corresponding module API file, wherein the interface is used for calling the API parent file to carry out the network request. According to the method, module differentiation and classification are carried out according to project scenes, module API files are established according to the modules, namely, the modules are disassembled according to the project scenes, all APIs are not gathered together, and the coupling degree is low. For classification reasons, the total amount of traffic effectuators required to write by the network layer is reduced, reducing the effort as a whole. In addition, the parent class is set to close when requesting, namely, network requests are not carried out on all subclasses, and the network request method is put into the parent class to be executed, so that customization of a classification level is realized, customization is enhanced generally, and the aggregation degree is higher.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. Wherein:
FIG. 1 is a flow chart of an embodiment of an API management method provided by the present invention;
FIG. 2 is a flow chart of an embodiment of a method for requesting an API in accordance with the present invention;
FIG. 3 is a block diagram of an API management apparatus provided by the present invention;
FIG. 4 is a block diagram of an API management device provided by the present invention;
fig. 5 is a schematic structural diagram of an embodiment of a computer readable storage medium according to the present invention.
Detailed Description
The technical solutions 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 for purposes of illustration only and are not intended to limit the scope of the invention. It should be further noted that, for convenience of description, only some, but not all methods and processes related to the present invention are shown in the accompanying drawings. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "comprising" and "having" and any variations thereof herein are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may 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 may be included in at least one embodiment of the invention. The appearances of such phrases 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. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In software engineering, high cohesive and low coupling are criteria for judging whether a code is designed well or not, and particularly when an object-oriented program is designed, whether cohesive property of a class is high or not and whether coupling degree is low or not are judged. The purpose 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 the functional measure of the links within a module, and a good cohesive module should do exactly one thing. Coupling is a measure of the interconnection between modules in a software architecture, and the strength of coupling depends on the complexity of the interfaces between the modules, the point of entry or access to a module, and the data passing through the interface.
Besides high cohesion and low coupling, in software engineering, there is a concept of a parent class, that is, two classes (files) are relationships between a parent and a child, and the child may inherit functions (disclosure methods) of the parent class, for example, in the embodiment of the present invention, the parent class may be an apimode, and the child class may be AApis, BApis, CApis., that is, the AApis, BApis, CApis file has functions of the apimode (that is, the child class AApis, BApis, CApis and other subclasses may call the disclosure methods of the apimode of the parent class to implement the disclosure functions), so that the apimode may write a closing-in of functions required by some subclasses, that is, the parent class encapsulates basic functions.
The method combines the existing main stream API management mode in the current market, has the advantages of being high in strength and short in length, decoupling (decomposing into AApis, BApis, CApis and other subclasses) is carried out through service classification and father-son class design, and a mode of closing up (AApis, BApis, CApis and other subclasses realize the function method disclosed by father class APIMananager) is requested to be carried out on a network to realize high strength, so that the structure of high strength and low coupling of the API codes is realized.
As shown in fig. 1, an embodiment of the present invention provides an API management method, including:
step 10, constructing an API parent class file, wherein the API parent class file can be used for network requests;
step 20, carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules;
step 30, receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, and opening an interface of the project scene in the corresponding module API file, wherein the interface is used for calling the API parent file to perform the network request.
The beneficial effects of the invention are as follows: different from the prior art, the Application Programming Interface (API) management method provided by the invention comprises the steps of constructing an API parent file, wherein the API parent file can be used for network requests; carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules; and receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, and opening an interface of the project scene in the corresponding module API file, wherein the interface is used for calling the API parent file to carry out the network request. According to the method, module differentiation and classification are carried out according to project scenes, module API files are established according to the modules, namely, the modules are disassembled according to the project scenes, all APIs are not gathered together, and the coupling degree is low. For classification reasons, the total amount of traffic effectuators required to write by the network layer is reduced, reducing the effort as a whole. In addition, the parent class is set to close when requesting, namely, network requests are not carried out on all subclasses, and the network request method is put into the parent class to be executed, so that customization of a classification level is realized, customization is enhanced generally, and the aggregation degree is higher.
Further, the construction of the API parent file specifically includes:
writing the public function of the API parent class file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, the APP uploads data to the server and the APP downloads data.
Specifically, firstly, writing a public function (AApis, BApis, CApis and other functions commonly required by subclasses) on an API parent file (APIManager), integrating a series of public functions, such as public function packages of pulling data (APP requests data from a server), reporting data (APP uploads data to the server), APP downloading and the like, and not relating to specific business logic;
further, each module API file stores the 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 classification is performed according to the project scene, and the module API file establishment according to the module specifically comprises:
and carrying out module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the project, wherein the module API files comprise different subclasses.
Specifically, the module differentiation classification is carried out on the projects, and according to different project scenes, each module establishes an API management class (AApis, BApis, CApis..) which is a module API file, each API management class only stores the network request interface of the module, and only calls the method provided by the father class to carry out network request, and does not process specific request logic and data logic.
Further, the interface is configured to call the API parent file to perform a network request specifically includes:
the interface is used for calling the public function of the API parent file to carry out network request.
In the specific business code writing process, when the project scene of the network request is involved, the API writing is directly carried out in the corresponding module API management class (namely the corresponding module API file, such as BApis)
For example: the pulling of order data is needed in the B module, and a network request is needed, and at the moment, an interface- (void) getOrderDataFromServer for pulling the order data is needed to be opened in BApis class;
the specific implementation of the interface is to call a method in the parent class apimanagement to make a network request.
The key point of the invention is that the service modules of different project scenes are disassembled by API, module API files are built according to the modules, namely, the service according to the project is divided into AApis, BApis, CApis and other subclasses, and all APIs are not gathered together, namely, low coupling is realized;
in addition, the API parent file is set to close when the request is made, namely, network requests are not made in all subclasses, and a public function (public function) method is put into a parent high-level language application programming interface (HLLApi manager) to be executed so as to achieve high cohesion;
in the specific service code writing process, the subclasses AApis, BApis, CApis and the like of the service codes requiring the network do not relate to specific network request logic, and the network request codes of the parent class HLLApi manager do not relate to specific service logic;
when developing different service modules, the specific request mode of the API parent file is not needed, only the interface of the API parent file is required to be called for network request, the module API file is only managed by the API interface and is not required to be specifically requested by the network, the classification of the APIs is carried out according to the module, and the APIs of the module are not required to be provided with Manager files, and are placed in a subclass, so that intensive placement in the same class can be avoided, a large number of class files are not needed to be generated like discrete, the service logic and the technical logic with clear high-cohesion low-coupling design mode in software engineering are met, and the defects of the intensive API management mode and the discrete API management mode in the prior art are overcome.
The embodiment of the invention mainly solves the pain point of the API management mode existing in the prior art in the development of the iOS app, optimizes the experience of a developer by optimizing the code structure, thereby improving the development efficiency and the robustness of the code, and ensuring that the code has more expansibility and a code logic structure is clearer.
As shown in fig. 2, the embodiment of the present invention further provides an API requesting method, including:
step 60, initiating a network request;
step 70, matching corresponding module API files according to the project scene of the network request, and calling interfaces of the project scene in the corresponding module API files, wherein the interfaces are used for calling API parent class files to perform the network request;
and step 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 a method implemented by the API management method according to the above embodiment, and the process of initiating a network request and returning template data to the network demand initiator is implemented together. The application programming interface API request method of the present embodiment and the application programming interface API management method of the foregoing embodiments are based on the same inventive concept, and specific implementation processes of the application programming interface API request method are detailed in the method embodiment, and technical features of the foregoing embodiments are correspondingly applicable in the present embodiment, and are not described in detail herein.
According to the above-described embodiment, as shown in fig. 3, the embodiment of the present invention further provides an application programming interface API management device 50, the application programming interface API management device 100 including:
a building module 51, configured to build an API parent file, where the API parent file may be used for a network request;
the classifying and establishing module 52 is configured to perform module differentiation classification according to project scenes, and establish module API files according to modules;
the receiving and opening module 53 is configured to receive a network request requirement, match a corresponding module API file according to a project scene of the network request requirement, and open an interface of the project scene in the corresponding module API file, where the interface is configured to call the API parent file to perform a network request.
The application programming interface API management device of the present embodiment and the application programming interface API management method of the foregoing embodiments are based on the same inventive concept, and specific implementation processes thereof are detailed in the method embodiment, and technical features of the foregoing application programming interface API management method embodiment are correspondingly applicable in the present embodiment, and are not described in detail herein.
As shown in fig. 4, the embodiment of the present invention also provides an application programming interface API management device 100.
The application programming interface 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-described API management method.
The application programming interface API management device 100 includes:
a memory 120 for storing a computer program;
a processor 110 for implementing the steps of the application programming interface API management method as described above when executing the computer program.
The application programming interface API management apparatus of the present embodiment and the application programming interface API management method of the foregoing embodiments are based on the same inventive concept, and specific implementation processes thereof are detailed in the method embodiment, and technical features of the foregoing application programming interface API management method embodiment are correspondingly applicable in the present embodiment, and are not described in detail herein.
Referring specifically to fig. 5, fig. 5 is a schematic structural diagram of an embodiment of a computer readable storage medium according to the present invention.
Included in computer readable storage medium 200 is program data 210. The program data 210, when executed by a processor, may implement the application programming interface API management methods described above.
Unlike the prior art, the present invention provides an application programming interface API management method.
The beneficial effects of the invention are as follows: different from 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; carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules; and receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, and opening an interface of the project scene in the corresponding module API file, wherein the interface is used for calling the API parent file to carry out the network request. According to the method, module differentiation and classification are carried out according to project scenes, module API files are established according to the modules, namely, the modules are disassembled according to the project scenes, all APIs are not gathered together, and the coupling degree is low. For classification reasons, the total amount of traffic effectuators required to write by the network layer is reduced, reducing the effort as a whole. In addition, the parent class is set to close when requesting, namely, network requests are not carried out on all subclasses, and the network request method is put into the parent class to be executed, so that customization of a classification level is realized, customization is enhanced generally, and the aggregation degree is higher.
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 (10)
1. An API management method, comprising:
constructing an API parent class file, wherein the API parent class file can be used for network requests;
carrying out module differentiation classification according to project scenes, and establishing module API files according to the modules;
receiving a network request demand, matching a corresponding module API file according to a project scene of the network request demand, 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 according to claim 1, wherein the constructing an API parent file specifically comprises:
writing the public function of the API parent class file, and integrally managing the public function, wherein the public function comprises the following encapsulated functions: the APP requests data from the server, the APP uploads data to the server and the APP downloads data.
3. The method of claim 2, wherein each module API file houses a network request interface for the module and is capable of invoking a public function of the API parent file for a network request.
4. The method of claim 3, wherein the interface for invoking the API parent file for a network request specifically comprises:
the interface is used for calling the public function of the API parent file to carry out network request.
5. The method of claim 4, wherein the classifying module differentiation according to project scenes, and creating module API files according to modules specifically comprises:
and carrying out module differentiation classification on the service modules according to project scenes, and classifying the service modules into different subclasses according to the project, wherein the module API files comprise different subclasses.
6. The method of claim 5, wherein the public function is performed in a parent high-level language application programming interface.
7. An API requesting method, comprising:
initiating a network request;
matching corresponding module API files according to the project scene requested by the network, and calling interfaces of the project scene in the corresponding module API files; the interface is used for calling the API parent class 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 API management apparatus, comprising:
the construction module is used for constructing an API parent class file which can be used for network requests;
the classification and establishment module is used for carrying out module differentiation classification according to project scenes and establishing module API files according to the modules;
the receiving and opening module is used for receiving a network request demand, matching corresponding module API files according to project scenes of the network request demand, and opening interfaces of the project scenes in the corresponding module API files; the interface is used for calling the API parent file to carry out network request.
9. An API management device, characterized in that,
comprising the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the application programming interface API management method of any one of claims 1 to 6 when executing said computer program.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein program data for implementing the method according to any of claims 1-6 when being executed by a processor.
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 CN114844875A (en) | 2022-08-02 |
| CN114844875B true 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 (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110016124A (en) * | 2009-08-11 | 2011-02-17 | (주)시스포유아이앤씨 | Web contents managenment method in moduled web-client application framework using xml |
| CN102622229A (en) * | 2012-02-24 | 2012-08-01 | 北京星网锐捷网络技术有限公司 | Fusion method, fusion system and fusion device of development frameworks of different types |
| 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 |
| 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 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8201191B2 (en) * | 2004-06-30 | 2012-06-12 | Time Warner Cable Inc. | Apparatus and methods for implementation of network software interfaces |
| 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 |
| US9323587B2 (en) * | 2012-09-27 | 2016-04-26 | National Taiwan University | Method and system for automatic detecting and resolving APIs |
| CN108769249B (en) * | 2018-06-20 | 2021-05-25 | 武汉斗鱼网络科技有限公司 | iOS high-performance high-expansion network device, implementation method, server and medium |
| CN112346774A (en) * | 2019-08-06 | 2021-02-09 | 北京京东尚科信息技术有限公司 | Method and device for generating application installation package |
| CN112748908B (en) * | 2020-12-31 | 2024-02-27 | 广东广宇科技发展有限公司 | Method and device for developing Restful service based on SSM framework |
-
2022
- 2022-04-21 CN CN202210422967.3A patent/CN114844875B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110016124A (en) * | 2009-08-11 | 2011-02-17 | (주)시스포유아이앤씨 | Web contents managenment method in moduled web-client application framework using xml |
| CN102622229A (en) * | 2012-02-24 | 2012-08-01 | 北京星网锐捷网络技术有限公司 | Fusion method, fusion system and fusion device of development frameworks of different types |
| 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 |
| 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)
| Title |
|---|
| Http调用第三方接口的两种方式实例;Augenstern-month;CSDN;全文 * |
| 基于D3D的三维游戏引擎的设计与实现;樊翠等;科学技术与工程;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114844875A (en) | 2022-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104123151B (en) | The plug-in management method of application program, device and mobile terminal in mobile terminal | |
| EP2003854B1 (en) | Server for communicating with multi-mode devices using multi-mode applications | |
| US8082414B2 (en) | Method and system for centralized memory management in wireless terminal devices | |
| EP2418825A1 (en) | Method and system for generating open telecommunication service based on internet | |
| US8732652B2 (en) | System and method for creating multi-mode applications | |
| US9277033B2 (en) | Server for communicating with multi-mode devices using multi-mode applications | |
| JP2007511018A (en) | Method and apparatus for composing software | |
| CN102209111A (en) | Open cross-platform system for cloud computing mobile network terminal equipment | |
| WO2011060735A1 (en) | Method,device and system for invoking widget | |
| CN105959302B (en) | A kind of terminal management system and method | |
| KR100670605B1 (en) | System and method for servicing multimedia contents and recording medium thereof | |
| CN114024821A (en) | Northbound interface management method and device | |
| CN113296987B (en) | Interface calling method and device for calling module, computer equipment and storage medium | |
| CN114844875B (en) | Application programming interface API management method, device, equipment and medium | |
| CN112698930B (en) | Method, device, equipment and medium for obtaining server identification | |
| CN109683992B (en) | Method and apparatus for managing objects | |
| EP2003843B1 (en) | Device for communicating in multiple modes using multi-mode applications | |
| CN113296744A (en) | Application development system and method | |
| CN103677842A (en) | Software tool configuration type integrated expansion calling method and system | |
| CN108334374A (en) | The method and apparatus of component dynamic load and execution | |
| CN111104122A (en) | Method for mapping xml service logic to java service logic | |
| US20080311950A1 (en) | Device for communicating in multiple modes using multi-mode applications | |
| CN113347609B (en) | Wireless intelligent control platform | |
| CA2635173A1 (en) | System and method for creating multi-mode applications | |
| CN115378945A (en) | Management method and system based on cloud service |
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 |