WO2019136813A1 - Procédé de gestion de fichiers d'api, serveur, et support de stockage - Google Patents

Procédé de gestion de fichiers d'api, serveur, et support de stockage Download PDF

Info

Publication number
WO2019136813A1
WO2019136813A1 PCT/CN2018/077655 CN2018077655W WO2019136813A1 WO 2019136813 A1 WO2019136813 A1 WO 2019136813A1 CN 2018077655 W CN2018077655 W CN 2018077655W WO 2019136813 A1 WO2019136813 A1 WO 2019136813A1
Authority
WO
WIPO (PCT)
Prior art keywords
api
file
api file
interface
server
Prior art date
Application number
PCT/CN2018/077655
Other languages
English (en)
Chinese (zh)
Inventor
叶腾飞
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019136813A1 publication Critical patent/WO2019136813A1/fr

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

Definitions

  • the present application relates to the field of computer technologies, and in particular, to an application programming interface (API) file management method, a server, and a computer readable storage medium.
  • API application programming interface
  • the API file is a descriptive file about API interface calls.
  • Each API file includes API interface and API interface call instructions.
  • the present application provides an API file management method, a server, and a computer readable storage medium, which can perform real-time monitoring on an API interface, improve the readability of the code, and facilitate timely modification and notification of the client when the API interface is changed. .
  • an API file management method including:
  • Receiving step receiving an API file newly uploaded by the server
  • the judging step is: determining, according to the interface name in the API file, whether the interface is a stored API file that is changed by the interface, or a new API file, and if the interface is a stored API file, the prompt information in the preset format is sent to the client, and the process ends. If the API file is added, the process enters the allocation step;
  • Assignment step assign a label to the API code and API file of the newly added API interface, and establish a mapping relationship between the API code and the API file through the label;
  • Setup steps Set the association between the tag and the client address.
  • the method further comprises: separating the code of the API interface from the API file in the server, providing a code library storage API code, and an API file library storage API file.
  • the determining step further includes:
  • the API file Comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library. If the interface name of the newly uploaded API file is the same as the interface name of an API file stored in the API file library, then The API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library, it is determined that the API file is a new API file.
  • the method further includes: after the setting of the association relationship between the label and the client address is completed, sending the feedback information in a preset format to the server.
  • the tags automatically generate a unique tag name based on the order of the tag list.
  • the present application also provides a server, the server includes: a memory, a processor, a display, and an API file management program stored on the memory and executable on the processor, where the API file management program is The processor executes, and the following steps can be implemented:
  • Receiving step receiving an API file newly uploaded by the server
  • the judging step is: determining, according to the interface name in the API file, whether the interface is a stored API file that is changed by the interface, or a new API file. If the interface of the stored API file is changed, the prompt information of the preset format is sent to the client, and the process ends. If the API file is added, the process enters the allocation step;
  • Assignment step assign a label to the API code and API file of the newly added API interface, and establish a mapping relationship between the API code and the API file through the label;
  • Setup steps Set the association between the tag and the client address.
  • the API file management program is executed by the processor, and further implements the steps of: separating the code of the API interface from the API file in the server, providing a code library storage API code, and an API file library storage API file.
  • the determining step further includes:
  • the API file Comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library. If the interface name of the newly uploaded API file is the same as the interface name of an API file stored in the API file library, then The API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library, it is determined that the API file is a new API file.
  • the API file management program is executed by the processor, and the following steps are further implemented: after the setting of the association relationship between the tag and the client address is completed, the feedback information of the preset format is sent to the server.
  • the present application further provides a computer readable storage medium, where the computer readable storage medium includes an API file management program, and when the API file management program is executed by a processor, the foregoing can be implemented as described above. Any step in the API file management method.
  • the API file management method, the server and the computer readable storage medium proposed by the application by receiving an API file newly uploaded by the server, using the interface name in the API file to determine whether the interface is a stored API file changed, or is added
  • the API file if it is a stored API file of the interface change, sends a prompt message in a preset format to the client. If the API file is added, a label is added to the API code and the API file of the new API interface, and then the label is passed. Establish a mapping relationship between the API code and the API file, and finally set the association relationship between the tag and the client address, thereby effectively monitoring the API interface change, and modifying the changed API interface in time.
  • FIG. 1 is a schematic diagram of a preferred embodiment of a server of the present application.
  • FIG. 2 is a schematic diagram of an application environment of an API file management method according to the present application.
  • FIG. 3 is a block diagram showing a preferred embodiment of the API file management program in FIG. 1 or FIG. 2;
  • FIG. 4 is a flowchart of a preferred embodiment of an API file management method according to the present application.
  • FIG. 5 is a flowchart of a second embodiment of an API file management method according to the present application.
  • FIG. 1 it is a schematic diagram of a preferred embodiment of the server 1 of the present application.
  • the server 1 may be a server, a smart phone, a tablet computer, a personal computer, a portable computer, and other electronic devices having computing functions.
  • the server 1 includes a memory 11, a processor 12, a network interface 13, a communication bus 14, and an API file management program 10 stored on the memory 11 and executable on the processor 12.
  • the network interface 13 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), and is generally used to establish a communication connection between the server and other electronic devices.
  • Communication bus 14 is used to implement connection communication between these components.
  • the memory 11 includes at least one type of readable storage medium.
  • the at least one type of readable storage medium may be a non-volatile storage medium such as a flash memory, a hard disk, a multimedia card, a card type memory, or the like.
  • the memory 11 may be an internal storage unit of the server 1, such as a hard disk of the server 1.
  • the memory 11 may also be an external storage unit of the server 1, such as a plug-in hard disk equipped on the server 1, a smart memory card (SMC), and a secure digital ( Secure Digital, SD) cards, flash cards (FC cards), etc.
  • the memory 11 can be used not only for storing application software and various types of data installed in the server 1, such as an API file management program 10, an API interface code, an API file, etc., but also for temporarily Stores data that has been output or will be output, such as an interface class.
  • the processor 12 in some embodiments, may be a Central Processing Unit (CPU), microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing API file management.
  • CPU Central Processing Unit
  • microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing API file management.
  • the server 1 may also include a display, which may be referred to as a display screen or display unit.
  • the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an Organic Light-Emitting Diode (OLED) touch sensor.
  • OLED Organic Light-Emitting Diode
  • the display is used to display information processed in the server 1 and a work interface for displaying visualizations.
  • Figure 1 shows only server 1 having components 11-14 and computer program code for executing API file management program 10, but it should be understood that not all illustrated components may be implemented, alternative implementations may be more or more Less components.
  • the server 1 may further include an input unit such as a keyboard, a voice output device such as an audio, a headphone, and the like.
  • an input unit such as a keyboard
  • a voice output device such as an audio, a headphone, and the like.
  • the program code of the API file management program 10 is stored in the memory 11 as a computer storage medium.
  • the processor 12 executes the program code of the API file management program 10, the following steps are implemented:
  • Receiving step receiving an API file newly uploaded by the server
  • the judging step is: determining, according to the interface name in the API file, whether the interface is a stored API file that is changed by the interface, or a new API file, and if the interface is a stored API file, the prompt information in the preset format is sent to the client, and the process ends. If the API file is added, the process enters the allocation step;
  • Assignment step assign a label to the API code and API file of the newly added API interface, and establish a mapping relationship between the API code and the API file through the label;
  • Setup steps Set the association between the tag and the client address.
  • FIG. 2 it is a schematic diagram of an application environment of the API file management method of the present application.
  • the server 1 separates the API code from the API file, provides the API code library 15 to store the code of the API interface, and the API file library 16 stores the API file, but the API code library 15 and the API file library are collectively managed and distributed by the server 1.
  • the API file management program 10 receives an API file newly uploaded by the server 3, the API file management program 10 is started.
  • the API file is a descriptive file of an API interface, and each API file includes an API file interface name and an API interface call description, and the API interface call description includes a method, a function, a parameter, and the like in the API interface. .
  • the solution of the present application is explained by taking the face recognition interface as an example.
  • the API file management program 10 is started.
  • the server 3 refers to a provider of an API interface corresponding to the API file.
  • the client 4 refers to the caller of the API interface corresponding to the API file.
  • the server 3 provides a face recognition interface, and the client 4 invokes a face recognition interface for a face recognition application.
  • the API file management program 10 determines whether the API file is a stored API file of an interface change or a new API file by the interface name of the uploaded API file. If it is determined that the uploaded API file is a stored API file of the interface change, the interface change prompt information of the preset format is sent to the client 4. For example, if the API file is a stored API file whose face recognition API interface is changed by the interface name of the uploaded API file, the interface change prompt information is sent to the client 4, for example, “the face recognition API interface has been changed. The new interface is ***".
  • the specific judging method includes: comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library 16, if the interface name of the newly uploaded API file is stored in the API file library 16 If the interface name of an API file is the same, it is determined that the API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library 16, it is determined.
  • This API file is a new API file.
  • the API interface name of the newly uploaded API file is a face recognition API interface. If the API file library 16 also stores the face recognition API interface, the newly uploaded API file and the API file library 16 store the API file API interface call. If the description is different, the uploaded API file is a stored API file of the interface change; if the API file library 16 does not store the face recognition API interface, the uploaded API file is a newly added API file.
  • the API file management program 10 assigns a label to the API code and the API file of the newly added API interface, and establishes a mapping relationship between the API code and the API file through the label.
  • the tag is a unique tag name automatically generated according to the order of the tag list 17, and the tag list refers to a file for storing tags.
  • the newly uploaded age prediction API interface file is a new API file
  • the largest tag number stored in the tag list is the tag 022
  • the API file management program 10 automatically generates a tag 023 according to the tag list 17 in order, and the tag is 023 is assigned to the API code and API file of the age prediction API interface, and the mapping relationship between the API code of the age prediction API interface and the API file is established through the tag 023.
  • the API file management program 10 sets the association relationship between the tag and the client 4 address, and sends a message prompting the interface change to the client 4 when the interface in the API file is changed.
  • the client 4 refers to the caller of the API interface corresponding to the API file. For example, the association relationship between the label 023 and the client address is set.
  • the interface change prompt information is sent to the client 4, for example, “the age prediction API interface has changed, and the new interface is *** ".
  • the API file management method proposed by the above embodiment is different from the rest style API file management method and the markdown file management method.
  • the rest style API file adds a large number of comments in the code, that is, the code is combined with the API file to reduce the code readability.
  • the markdown file and the API file mentioned in this article are separated from the API file, but the markdown file needs to be manually described.
  • the code and API file of the markdown file are managed by the backend and frontend respectively, and the update is not synchronized when the API interface is changed. The separation of human collaboration is poor.
  • the API files and code mentioned in this article are managed by the background. It can effectively monitor the changes or additions of the API interface, so that the client interface can be notified in time when the API interface is changed, to avoid code intrusion. .
  • the media file processing program 10 may also be divided into one or more modules, one or more modules are stored in the memory 11 and executed by one or more processors (this implementation) The example is executed by the processor 12) to complete the application.
  • FIG. 3 it is a block diagram of a preferred embodiment of the API file management program 10 of FIG. 1 or 2.
  • a module as referred to in this application refers to a series of computer program instructions that are capable of performing a particular function.
  • the API file management program 10 includes: a receiving module 110, a determining module 120, an allocating module 130, and a setting module 140.
  • the functions or operating steps implemented by the modules 110-140 are similar to the above. No more detailed, by way of example, such as:
  • the receiving module 110 is configured to receive an API file newly uploaded by the server;
  • the determining module 120 is configured to determine, according to the interface name in the API file, whether the interface is a stored API file that is changed by the interface, or a new API file, and if the interface is a stored API file, the prompt information of the preset format is sent to the client. The process ends. If the API file is added, the process enters the allocation step;
  • the distribution module 130 is configured to allocate a label for the API code and the API file of the newly added API interface, and establish a mapping relationship between the API code and the API file through the label;
  • the setting module 140 is configured to set an association relationship between the label and the client address.
  • FIG. 4 it is a flowchart of a preferred embodiment of the API file management method of the present application.
  • the implementation of the API file management method includes steps S10-S60:
  • step S10 when the API file management program 10 receives an API file newly uploaded by the server 3, the API file management program 10 is started.
  • the API file is a descriptive file of an API interface, and each API file includes an API file interface name and an API interface call description, and the API interface call description includes a method, a function, a parameter, and the like in the API interface. .
  • the solution of the present application is explained by taking the face recognition interface as an example.
  • the API file management program 10 is started.
  • the server 3 refers to a provider of an API interface corresponding to the API file.
  • the client 4 refers to the caller of the API interface corresponding to the API file.
  • the server 3 provides a face recognition interface, and the client 4 invokes a face recognition interface for a face recognition application.
  • step S20 the API file management program 10 determines whether the API file is a stored API file of the interface change or a new API file by using the interface name of the uploaded API file.
  • step S30 if it is determined that the uploaded API file is a stored API file of the interface change, step S40 is performed. If it is determined that the uploaded API file is a new API file, step S50 is performed.
  • the specific judging method includes: comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library 16, if the interface name of the newly uploaded API file is stored in the API file library 16 If the interface name of an API file is the same, it is determined that the API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library 16, it is determined. This API file is a new API file.
  • the API interface name of the newly uploaded API file is a face recognition API interface. If the API file library 16 also stores the face recognition API interface, the newly uploaded API file and the API file library 16 store the API file API interface call. If the description is different, the uploaded API file is a stored API file of the interface change; if the API file library 16 does not store the face recognition API interface, the uploaded API file is a newly added API file.
  • step S40 the API file management program 10 sends the prompt information of the preset format to the client 4.
  • the API file is a stored API file whose face recognition API interface is changed by the interface name of the uploaded API file
  • the interface change prompt information is sent to the client 4, for example, “the face recognition API interface has been changed.
  • the new interface is ***".
  • step S50 if the uploaded API file is a newly added API file, the API file management program 10 assigns a label to the API code and the API file of the newly added API interface, and establishes a mapping relationship between the API code and the API file through the label.
  • the tag is a unique tag name automatically generated in order according to the tag list 17.
  • the newly uploaded age prediction API interface file is a new API file, and the largest tag number stored in the tag list is the tag 022, and the API file management program 10 automatically generates a tag 023 according to the tag list 17 in order, and the tag is 023 is assigned to the API code and API file of the age prediction API interface, and the mapping relationship between the API code of the age prediction API interface and the API file is established through the tag 023.
  • step S60 the API file management program 10 sets the association relationship between the tag and the client address, and sends a message prompting the interface change to the client 4 when the interface in the API file is changed.
  • the client 4 refers to the caller of the API interface corresponding to the API file. For example, the association relationship between the label 023 and the client address is set, and when the subsequent age prediction interface is changed, the interface change prompt information is sent to the client 4, for example, “the age prediction API interface has changed, and the new interface is *** ".
  • the API file management method proposed in the foregoing embodiment determines the API uploaded by the server 3, and if the API file is changed by the interface, sends the prompt information in the preset format to the client 4, and if it is a new API file, assigns a
  • the tag establishes a mapping relationship between the API code and the API file, and then binds the tag to the client address, thereby effectively monitoring the interface change, and can notify the client 4 in time to avoid code intrusion.
  • FIG. 5 it is a flowchart of the second embodiment of the API file management method of the present application.
  • the implementation of the API file management method includes steps S10-S70:
  • step S10 when the API file management program 10 receives an API file newly uploaded by the server 3, the API file management program 10 is started.
  • the API file is a descriptive file of an API interface, and each API file includes an API file interface name and an API interface call description, and the API interface call description includes a method, a function, a parameter, and the like in the API interface. .
  • the solution of the present application is explained by taking the face recognition item as an example.
  • the API file management program 10 is started.
  • the server 3 refers to a provider of an API interface corresponding to the API file.
  • the client 4 refers to the caller of the API interface corresponding to the API file.
  • the server 3 provides a face recognition interface, and the client 4 invokes a face recognition interface for a face recognition application.
  • step S20 the API file management program 10 determines whether the API file is a stored API file of the interface change or a new API file by using the interface name of the uploaded API file.
  • step S30 if it is determined that the uploaded API file is a stored API file of the interface change, step S40 is performed. If it is determined that the uploaded API file is a new API file, step S50 is performed.
  • the specific judging method includes: comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library 16, if the interface name of the newly uploaded API file is stored in the API file library 16 If the interface name of an API file is the same, it is determined that the API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library 16, it is determined. This API file is a new API file.
  • the API interface name of the newly uploaded API file is a face recognition API interface. If the API file library 16 also stores the face recognition API interface, the newly uploaded API file and the API file library 16 store the API file API interface call. If the description is different, the uploaded API file is a stored API file of the interface change; if the API file library 16 does not store the face recognition API interface, the uploaded API file is a newly added API file.
  • step S40 the API file management program 10 sends the prompt information of the preset format to the client 4.
  • the API file is a stored API file whose face recognition API interface is changed by the interface name of the uploaded API file
  • the interface change prompt information is sent to the client 4, for example, “the face recognition API interface has been changed.
  • the new interface is ***".
  • step S50 if the uploaded API file is a newly added API file, the API file management program 10 assigns a label to the API code and the API file of the newly added API interface, and establishes a mapping relationship between the API code and the API file through the label.
  • the tag is a unique tag name automatically generated in order according to the tag list 17.
  • the newly uploaded age prediction API interface file is a new API file, and the largest tag number stored in the tag list is the tag 022, and the API file management program 10 automatically generates a tag 023 according to the tag list 17 in order, and the tag is 023 is assigned to the API code and API file of the age prediction API interface, and the mapping relationship between the API code of the age prediction API interface and the API file is established through the tag 023.
  • step S60 the API file management program 10 sets the association relationship between the tag and the client address, and sends a message prompting the interface change to the client 4 when the interface in the API file is changed.
  • the client address may be an IP address or a mailbox.
  • the client 4 refers to the caller of the API interface corresponding to the API file. For example, the association relationship between the label 023 and the client address is set.
  • the interface change prompt information is sent to the client 4, for example, “the age prediction API interface has changed, and the new interface is *** ".
  • step S70 after the setting relationship between the label and the client address is completed, the API file management program 10 sends the feedback information in the preset format to the server 3.
  • the feedback information may be sent to the server 3 by using a mailbox or a short message. For example, after the association between the label and the client address is set, the feedback information is sent to the mailbox of the server 3, for example, “the label corresponding to the newly added age prediction API interface is set”.
  • the failure prompt information may be set in the assigning step or the setting step, and the failure prompt for sending the preset format to the mailbox of the server 3 when the label is assigned or the association between the label and the client address fails.
  • Information and reasons for failure For example, if the association between the label and the client address fails, the feedback message is sent to the mailbox of the server 3, for example, the label setting corresponding to the newly added *** API interface fails, and the reason for the failure is ***, please handle it in time. Or "The new *** API interface *** failed for the following reasons: ***, please handle it in time.”
  • the API file management method proposed in this embodiment sends feedback information to the server 3 after setting the association relationship between the tag and the client address, thereby improving real-time monitoring of the API file management.
  • the API file update fails, it will be processed in time.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium includes an API file management program 10, and when the API file management program 10 is executed by the processor, the following operations are implemented:
  • Receiving step receiving an API file newly uploaded by the server
  • the judging step is: determining, according to the interface name in the API file, whether the interface is a stored API file that is changed by the interface, or a new API file. If the interface of the stored API file is changed, the prompt information of the preset format is sent to the client, and the process ends. If the API file is added, the process enters the allocation step;
  • Assignment step assign a label to the API code and API file of the newly added API interface, and establish a mapping relationship between the API code and the API file through the label;
  • Setup steps Set the association between the tag and the client address.
  • the method further comprises: separating the code of the API interface from the API file in the server, providing a code library storage API code, and an API file library storage API file.
  • the determining step further includes:
  • the API file Comparing the interface name of the newly uploaded API file with the interface name of the API file stored in the API file library. If the interface name of the newly uploaded API file is the same as the interface name of an API file stored in the API file library, then The API file is a stored API file of the interface change. If the interface name of the newly uploaded API file is different from the interface name of all the API files stored in the API file library, it is determined that the API file is a new API file.
  • the method further includes: after the setting of the association relationship between the label and the client address is completed, sending the feedback information in a preset format to the server.
  • the tags automatically generate a unique tag name based on the order of the tag list.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un procédé de gestion de fichiers d'API, un serveur, et un support de stockage, ledit procédé comportant les étapes consistant à: recevoir un fichier d'API nouvellement téléchargé par un serveur; déterminer, d'après un nom d'interface dans le fichier d'API, si le fichier d'API est un fichier d'API stocké dont l'interface a été changée ou un fichier d'API nouvellement ajouté; si le fichier d'API est un fichier d'API stocké dont l'interface a été changée, envoyer, à un client, des informations d'invite présentant un format prédéterminé, et mettre fin au processus; si le fichier d'API est un fichier d'API nouvellement ajouté, affecter une étiquette à un code d'API d'une interface d'API nouvellement ajoutée et au fichier d'API, et établir, au moyen de l'étiquette, une relation de mappage entre le code d'API et le fichier d'API; et spécifier une relation d'association entre l'étiquette et l'adresse du client, de façon à surveiller efficacement la migration de l'interface et à éviter une intrusion de code.
PCT/CN2018/077655 2018-01-11 2018-02-28 Procédé de gestion de fichiers d'api, serveur, et support de stockage WO2019136813A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810026284.XA CN108427560A (zh) 2018-01-11 2018-01-11 Api文件管理方法、服务器及存储介质
CN201810026284.X 2018-01-11

Publications (1)

Publication Number Publication Date
WO2019136813A1 true WO2019136813A1 (fr) 2019-07-18

Family

ID=63155881

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077655 WO2019136813A1 (fr) 2018-01-11 2018-02-28 Procédé de gestion de fichiers d'api, serveur, et support de stockage

Country Status (2)

Country Link
CN (1) CN108427560A (fr)
WO (1) WO2019136813A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109144501A (zh) * 2018-08-30 2019-01-04 杭州数澜科技有限公司 一种通过标签生成api的方法和系统
CN109710301A (zh) * 2018-11-30 2019-05-03 福建天泉教育科技有限公司 一种自动比较接口文档差异的方法及终端
CN111198818B (zh) * 2019-12-30 2023-02-24 北京中网易企秀科技有限公司 一种信息获取方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101814084A (zh) * 2010-01-11 2010-08-25 北京世纪高通科技有限公司 Api管理方法及系统
CN104484216A (zh) * 2014-12-29 2015-04-01 广州唯品会网络技术有限公司 服务接口文档和在线测试工具生成方法、装置
CN107291459A (zh) * 2017-06-09 2017-10-24 深圳市金立通信设备有限公司 一种整理信息的方法及服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090210861A1 (en) * 2008-02-20 2009-08-20 Mariana Alupului Dita doclet tool and method for extracting and analyzing api documentation
CN103049271B (zh) * 2012-12-27 2016-01-27 微梦创科网络科技（中国）有限公司 自动生成api接口的描述文档的方法和装置
CN105045577B (zh) * 2015-06-29 2018-12-18 用友优普信息技术有限公司 接口变更的提示方法和接口变更的提示系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101814084A (zh) * 2010-01-11 2010-08-25 北京世纪高通科技有限公司 Api管理方法及系统
CN104484216A (zh) * 2014-12-29 2015-04-01 广州唯品会网络技术有限公司 服务接口文档和在线测试工具生成方法、装置
CN107291459A (zh) * 2017-06-09 2017-10-24 深圳市金立通信设备有限公司 一种整理信息的方法及服务器

Also Published As

Publication number Publication date
CN108427560A (zh) 2018-08-21

Similar Documents

Publication Publication Date Title
WO2020220638A1 (fr) Procédé et appareil d'association d'un système de liaison à un système de journalisation, et support de stockage
CN108055248B (zh) 基于dubbo框架的远程调用方法、服务器及存储介质
WO2019104973A1 (fr) Procédé d'invocation de langage croisé, serveur et support d'informations
CN110347560B (zh) 大数据产品的异常提示方法、装置、系统、设备及介质
WO2019062182A1 (fr) Procédé et dispositif de synchronisation de données, et support de stockage lisible par ordinateur
CN110427252B (zh) 基于任务依赖关系的任务调度方法、装置及存储介质
WO2022027867A1 (fr) Procédé et appareil de suivi de lien multifil basé sur mdc, et support de stockage lisible par ordinateur
WO2019148722A1 (fr) Dispositif électronique, procédé de migration et d'appel de données, et support d'informations
WO2019075774A1 (fr) Procédé et appareil de configuration de paramètres de dispositif, dispositif informatique, et support de stockage
WO2019061991A1 (fr) Procédé de modélisation de plateforme de modèle universel à éléments multiples, dispositif électronique, et support d'informations lisible par ordinateur
US10110549B2 (en) Method, server and electronic devices of synchronizing notification messages for electronic devices
WO2019136813A1 (fr) Procédé de gestion de fichiers d'api, serveur, et support de stockage
WO2020082558A1 (fr) Procédé de réglage de point d'arrêt basé sur un nom de fonction, dispositif, appareil informatique et support de stockage
WO2019041441A1 (fr) Procédé et dispositif de mise à jour pour une vue de liste et support de stockage lisible par ordinateur
WO2020015170A1 (fr) Appareil et procédé d'invocation d'interface, et support d'informations lisible par ordinateur
US11061669B2 (en) Software development tool integration and monitoring
CN106528301B (zh) 超时等待时长更新方法及装置
WO2021169275A1 (fr) Procédé et appareil d'accès à un dispositif de réseau sdn, dispositif informatique et support de stockage
WO2021013056A1 (fr) Procédé et appareil de traitement de données basés sur un microservice, dispositif, et support de stockage lisible
WO2021022714A1 (fr) Procédé de traitement de message destiné à un nœud entre des chaînes de blocs, dispositif, appareil et support
CN110851248A (zh) 异步任务数据处理方法、装置及计算机可读存储介质
US9706006B2 (en) System and method of context aware adaption of content for a mobile device
WO2017084490A1 (fr) Procédé et dispositif pour télécharger des données
WO2019062180A1 (fr) Procédé de transfert de tâches par réseau, et dispositif et support de stockage
WO2017124801A1 (fr) Procédé, dispositif, et système de lanceement d'une instanciation vnf

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18900373

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12.10.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18900373

Country of ref document: EP

Kind code of ref document: A1