WO2019136813A1

WO2019136813A1 - Api file management method, server, and storage medium

Info

Publication number: WO2019136813A1
Application number: PCT/CN2018/077655
Authority: WO
Inventors: 叶腾飞
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-01-11
Filing date: 2018-02-28
Publication date: 2019-07-18
Also published as: CN108427560A

Abstract

The present application discloses an API file management method, a server, and a storage medium, said method comprising: receiving an API file newly uploaded by a server; determining, according to an interface name in the API file, whether the API file is a stored API file having a changed interface or a newly added API file; if the API file is a stored API file having a changed interface, sending, to a client, prompt information having a predetermined format, and ending the process; if the API file is a newly added API file, assigning a label to an API code of a newly added API interface and the API file, and establishing, by means of the label, a mapping relationship between the API code and the API file; and setting an association relationship between the label and the address of the client, so as to effectively monitor the interface migration and avoid code intrusion.

Description

API file management method, server and storage medium

Priority claim

This application claims the priority of the Chinese Patent Application entitled "API File Management Method, Server and Storage Media" submitted by the Chinese Patent Office on January 11, 2018, with the application number 201810026284.X, the overall content of the Chinese patent application This application is incorporated by reference.

Technical field

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.

Background technique

The API file is a descriptive file about API interface calls. Each API file includes API interface and API interface call instructions. At present, there are two main types of API file management. One is to add a lot of comments in the code that implements the API interface, and automatically generate rest style API files through tools. This type of API file has strong code intrusion. Reduce the readability of the code; the other is to create a markdown file, add API interface description in the markdown file, this type of API file is difficult to modify in time when the interface is changed, and at the same time, multi-person collaboration, front-end separation In the scenario, the application is not working well.

Summary of the invention

In view of the above, 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. .

To achieve the above objective, the present application provides 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.

Preferably, 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.

Preferably, the determining step further 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. 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.

Preferably, 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.

Preferably, the tags automatically generate a unique tag name based on the order of the tag list.

In addition, 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;

Setup steps: Set the association between the tag and the client address.

Preferably, 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.

Preferably, the determining step further includes:

Preferably, 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.

In addition, in order to achieve the above object, 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.

DRAWINGS

1 is a schematic diagram of a preferred embodiment of a server of the present application;

2 is a schematic diagram of an application environment of an API file management method according to the present application;

3 is a block diagram showing a preferred embodiment of the API file management program in FIG. 1 or FIG. 2;

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.

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to limit the application.

As shown in FIG. 1, it is a schematic diagram of a preferred embodiment of the server 1 of the present application.

In this embodiment, 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. In some embodiments, the memory 11 may be an internal storage unit of the server 1, such as a hard disk of the server 1. In other embodiments, 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.

In this embodiment, 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. The computer program code of the program 10, and the like.

Preferably, the server 1 may also include a display, which may be referred to as a display screen or display unit. In some embodiments, 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. 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.

Preferably, 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.

In the embodiment of the server 1 shown in FIG. 1, the program code of the API file management program 10 is stored in the memory 11 as a computer storage medium. When 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;

Setup steps: Set the association between the tag and the client address.

In this embodiment, as shown in 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. 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. When the server 3 is newly uploaded with an API file about the face recognition API interface, 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. For example, 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. For example, 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.

Assuming that the uploaded API file is a new 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. For example, 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.

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. 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 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. .

Optionally, in other embodiments, 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.

As shown in 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.

In this embodiment, 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.

As shown in FIG. 4, it is a flowchart of a preferred embodiment of the API file management method of the present application.

In the present embodiment, when the processor 12 executes the computer program of the API file management program 10 stored in the memory 11, the implementation of the API file management method includes steps S10-S60:

In 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. When the server 3 is newly uploaded with an API file about the face recognition API interface, 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. For example, the server 3 provides a face recognition interface, and the client 4 invokes a face recognition interface for a face recognition application.

In 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.

In 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. For example, 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.

In step S40, the API file management program 10 sends the prompt information of the preset format 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 ***".

In 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. Wherein, the tag is a unique tag name automatically generated in order according to the tag list 17. For example, 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.

In 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.

As shown in FIG. 5, it is a flowchart of the second embodiment of the API file management method of the present application.

In the present embodiment, when the processor 12 executes the computer program of the API file management program 10 stored in the memory 11, the implementation of the API file management method includes steps S10-S70:

In 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. When the server 3 is newly uploaded with an API file about the face recognition API interface, 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. For example, the server 3 provides a face recognition interface, and the client 4 invokes a face recognition interface for a face recognition application.

In 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. 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 *** ".

In 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”.

In another embodiment, 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."

Compared with the first embodiment, 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. When the API file update fails, it will be processed in time.

In addition, 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;

Setup steps: Set the association between the tag and the client address.

Preferably, the determining step further includes:

The specific implementation manner of the computer readable storage medium of the present application is substantially the same as the specific implementation manner of the foregoing API file management method, and details are not described herein again.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a series of elements includes those elements. It also includes other elements not explicitly listed, or elements that are inherent to such a process, device, item, or method. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, the device, the item, or the method that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, 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.

The above is only a preferred embodiment of the present application, and thus does not limit the scope of the patent application, and the equivalent structure or equivalent process transformation made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims

An API file management method is applied to a server, and the server is connected to the server and the client, and the method includes:

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 API file management method according to claim 1, further comprising: separating the code of the API interface from the API file in the server, providing the code library storage API code, and the API file library storage API file.
The API file management method according to claim 2, wherein 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.
The API file management method according to claim 3, wherein the API interface call description comprises: a method, a function of the class, and a related description of the parameter.
The API file management method according to claim 1, wherein the determining step further comprises:

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 method according to claim 1, further comprising: sending the feedback information of the preset format to the server after the association between the label and the client address is completed.
The API file management method according to any one of claims 6 to 4, wherein the tag automatically generates a unique tag name according to the order of the tag list.
A server, comprising: a memory, a processor and a display, wherein the memory stores an API file management program, and the API file management program is executed by the processor, 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, 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 server according to claim 8, wherein said API file management program is executed by said processor, and further comprising: separating a code of an API interface from an API file in a server, and providing a code library storage API Code, API file library storage API file.
The server according to claim 9, wherein 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.
The server according to claim 10, wherein the API interface call description comprises: a method, a function of a class, and a related description of the parameter.
The server according to claim 8, wherein the determining step further comprises:

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 server according to claim 8, wherein the API file management program is executed by the processor, and the following steps are further implemented: after the association between the label and the client address is completed, the preset format is sent. Feedback to the server.
The server according to claim 13, wherein said tag automatically generates a unique tag name in accordance with the order of the tag list.
A computer readable storage medium, comprising: an API file management program, wherein the system API file management program is executed by a processor to implement the following steps:

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 computer readable storage medium according to claim 15, wherein said API file management program is executed by said processor, and further comprising: separating a code of an API interface from an API file in a server, providing Code library storage API code, API file library storage API file.
The computer readable storage medium according to claim 16, wherein 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.
The computer readable storage medium according to claim 15, wherein the determining step further comprises:

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 computer readable storage medium according to claim 15, wherein the API file management program is executed by the processor, and further, the step of: sending the association relationship between the tag and the client address is completed, and then sending The feedback information of the preset format is sent to the server.
A computer readable storage medium according to claim 19, wherein said tag automatically generates a unique tag name based on the order of the tag list.