CN110704132B - Processing method and system of interface service pile - Google Patents
Processing method and system of interface service pile Download PDFInfo
- Publication number
- CN110704132B CN110704132B CN201910815217.0A CN201910815217A CN110704132B CN 110704132 B CN110704132 B CN 110704132B CN 201910815217 A CN201910815217 A CN 201910815217A CN 110704132 B CN110704132 B CN 110704132B
- Authority
- CN
- China
- Prior art keywords
- interface
- database
- interface service
- return value
- address
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a processing method and a system of an interface service pile, which define interface information of the interface service pile and the interface service pile, wherein the interface information comprises an interface address, a calling mode and a return value; searching whether an interface address of an interface service pile exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into a database; mapping an interface address binding occupier based on pathVariable to complete the release of the interface service stub; if the mapping result exists, the occupation character is mapped based on pathVariable, and the release of the interface service stub is completed. By the interface service pile processing method, the maintenance device maintains, creates and deletes the interface in the database, so that when a calling party calls the return value in the database, the calling party does not need to write a program again, and the calling efficiency is improved.
Description
Technical Field
The invention relates to the technical field of information, in particular to a method and a system for processing an interface service stub.
Background
In an information-based system, the presentation and processing of data is often multifaceted. Particularly, in an integrated system with a high resource integration degree, data is generally required to be called from different systems for displaying or other systems for processing the data are required to be called. For example, in an enterprise, there may be both human resources related office systems and financial processing related financial systems. When the personnel of the office system check or process the related matters of the wages, the interface of the financial system needs to be called, and when the wages are released at the end of a month, the financial system can call the wages data of the office system.
In the prior art, if any two systems are developed simultaneously or in a related interface development stage, a calling party is likely to wait for a called party due to inconsistency of development progress, difficulty and workload. At this time, the interface caller usually writes a section of code in the program as a return value, debugs by using the simulation data, and then completes joint debugging of the calling code after the called party interface is developed.
However, if the system of the calling party needs to call data in a plurality of systems, and the systems of a plurality of called parties are still in a development state, in order to enable the calling party to debug, a plurality of sections of codes need to be written in the program of the calling party as return values.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and a system for processing an interface service stub, where an interface in a database is maintained, created, and deleted by a maintenance device, so that when a calling party calls a return value in the database, the calling party does not need to write a program again, thereby improving calling efficiency.
In order to achieve the above object, the embodiments of the present invention provide the following technical solutions:
the first aspect of the invention discloses a processing method of an interface service stub, which comprises the following steps:
defining an interface service pile and interface information of the interface service pile, wherein the interface information comprises an interface address, a calling mode and a return value;
searching whether an interface address of the interface service stub exists in a database;
if the interface service pile does not exist, storing the interface information of the interface service pile into the database;
mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub;
and if so, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
Preferably, if the interface address of the interface service stub exists in the database, the method further includes:
and determining that the return value of the interface service stub is a target return value, and updating the return value corresponding to the interface address in the database to be the target return value.
Preferably, after the interface service stub is released, the method further includes:
resolving the occupation symbol based on the pathVariable to obtain the interface address;
reading a return value corresponding to the interface address in the database and the calling mode;
and completing the calling of the interface service stub based on the return value and the calling mode.
Preferably, before storing the interface information of the interface service stub in the database, the method further includes:
judging whether the quantity of the interface information stored in the database reaches a preset value or not;
and if the quantity of the interface information stored in the database reaches a preset value, deleting the old interface information currently stored in the database.
The second aspect of the present invention discloses a processing system for interface service stub, comprising:
the maintenance device is used for defining an interface service stub and interface information of the interface service stub, wherein the interface information comprises an interface address, a calling mode and a return value; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; if the identifier exists, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile;
and the interface release device is used for mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
Preferably, the first and second liquid crystal materials are,
the maintenance device is further configured to determine that the return value of the interface service stub is a target return value, and update the return value corresponding to the interface address in the database to the target return value.
Preferably, the first and second liquid crystal materials are,
the interface issuing device is further configured to analyze the occupation character based on the pathVariable to obtain the interface address; reading a return value corresponding to the interface address in the database and the calling mode; and completing the calling of the interface service pile based on the return value and the calling mode.
Preferably, the first and second liquid crystal materials are,
the maintenance device is also used for judging whether the quantity of the interface information stored in the database reaches a preset value; and if the quantity of the interface information stored in the database reaches a preset value, deleting the old interface information currently stored in the database.
According to the above content, the invention discloses a processing method and a system of an interface service stub, wherein the interface service stub and the interface information of the interface service stub are defined, and the interface information comprises an interface address, a calling mode and a return value; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile; and if so, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub. By the interface service pile processing method, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, the program does not need to be written again at the calling party, and the calling efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a processing method of an interface service stub according to an embodiment of the present invention;
fig. 2 is a flowchart of another interface service stub processing method according to an embodiment of the present invention;
fig. 3 is a flowchart of another processing method of an interface service stub according to an embodiment of the present invention;
fig. 4 is a flowchart of another interface service stub processing method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a processing system of an interface service stub according to an embodiment of 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 drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
An embodiment of the present invention provides a method for processing an interface service stub, referring to fig. 1, where the method for processing an interface service stub at least includes the following steps:
step S101: interface service stubs and interface information for the interface service stubs are defined.
In step S101, the interface information includes an interface address, a calling method, and a return value.
It should be noted that the interface address is a self-defined interface address, and the interface address corresponds to the call mode and the return value.
The calling mode comprises checking GET, establishing POST, updating PUT and deleting DELETE, and the calling party can call the interface service stub according to the calling mode through the defined calling mode.
It should be noted that the GET is used to issue a request to a specific resource. It should be noted that the GET method should not be used in operations that produce "side effects".
And the POST is used for submitting data to the specified resources to process requests. The data is contained in the request body. The POST request may result in the creation of a new resource and/or the modification of an existing resource.
And the PUT is used for uploading the latest content to a specified resource position.
The DELETE is to Request the server to DELETE the resource identified by the Request-URL.
The return value is data returned to the calling party by calling data through the defined interface address by the calling party.
Step S102: searching whether an interface address of the interface service stub exists in a database, and if the interface address of the interface service stub does not exist in the database, executing the step S103; if the interface address of the interface service stub exists in the database, step S105 is executed.
In step S102, the database is a memory for storing the interface address, the calling mode, and the return value of the interface service stub, and the database may be pre-established manually or automatically established each time the interface service stub is used.
It should be noted that, if the interface address of the defined interface service stub is found in the database, it is indicated that the interface service stub is created in advance in the database, or the interface service stub is used before, and at this time, it is not necessary to create the interface service stub in the database; if the interface address of the defined interface service stub is not found in the database, the fact that the defined interface service stub does not exist in the database is indicated.
Step S103: and storing the interface information of the interface service stub into the database.
In step S103, since the interface service stub is used later, the interface service stub needs to be created in the database, that is, the interface information of the service stub is stored in the database, and when the interface service stub needs to be used next time, the interface service stub can be directly called in the database.
Step S104: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
In step S104, since the interface address of the defined interface service stub exists in the database, the release of the interface service stub can be completed only by mapping the interface address binding occupier based on pathVariable.
Note that, by annotating pathVariable, after the interface service stub is released, no file is generated, and pathVariable is used as a credential for the interface address and the return value corresponding to the interface address, thereby completing the release of the interface service stub.
Step S105: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
It should be noted that the execution principle and the specific execution process of step S105 are the same as the execution principle and the specific execution process of step S104, and refer to step S104, which is not described herein again.
The method comprises the steps that interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub; and if so, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub. By the interface service pile processing method, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, the program does not need to be written again at the calling party, and the calling efficiency is improved.
Referring to fig. 2, for another interface service stub processing method disclosed in the embodiment of the present application, the interface service stub processing method specifically includes the following steps:
step S201: interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values.
Step S202: searching whether an interface address of the interface service stub exists in a database, and if the interface address of the interface service stub does not exist in the database, executing a step S203; if the interface address of the interface service stub exists in the database, step S205 is executed.
It should be noted that the execution principle and the specific execution process of step S201 and step S202 are the same as the execution principle and the specific execution process of step S101 and step S102 shown in fig. 1, and reference may be made to the above corresponding description, which is not described again here.
Step S203: and storing the interface information of the interface service stub into the database.
Step S204: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
It should be noted that the execution principle and the specific execution process of step S203 and step S204 are the same as the execution principle and the specific execution process of step S103 and step S104 shown in fig. 1, and reference may be made to the above corresponding description, which is not repeated herein.
Step S205: and determining that the return value of the interface service stub is a target return value, and updating the return value corresponding to the interface address in the database to be the target return value.
In step S205, since the return value of the defined interface service stub is different from the return value stored in the database by the interface service stub, the return value corresponding to the interface address in the database needs to be updated to the target return value, i.e. the defined return value.
Step S206: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
It should be noted that the execution principle and the specific execution process of step S206 are the same as the execution principle and the specific execution process of step S105 shown in fig. 1, and reference may be made to the above corresponding description, which is not repeated herein.
The method comprises the steps that interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile; if yes, determining that the return value of the interface service stub is a target return value, and updating the return value corresponding to the interface address in the database to be the target return value; and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub. By the interface service pile processing method, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, the program does not need to be written again at the calling party, and the calling efficiency is improved.
Referring to fig. 3, for another processing method of an interface service stub disclosed in the embodiment of the present application, the processing method of the interface service stub specifically includes the following steps:
step S301: defining an interface service stub and interface information of the interface service stub, wherein the interface information comprises an interface address, a calling mode and a return value.
Step S302: searching whether an interface address of the interface service stub exists in a database, and if the interface address of the interface service stub does not exist in the database, executing a step S303; if the interface address of the interface service stub exists in the database, step S307 is executed.
Step S303: and storing the interface information of the interface service stub into the database.
Step S304: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
Step S305: and determining the return value of the interface service stub as a target return value, and updating the return value corresponding to the interface address in the database as the target return value.
Step S306: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
It should be noted that the execution principle and the specific execution process of steps S301 to S306 are the same as the execution principle and the specific execution process of steps S201 to S206 shown in fig. 2, and reference may be made to the above corresponding description, which is not repeated herein.
Step S307: and resolving the occupation character based on the pathVariable to obtain the interface address.
In step S307, since the return value of the defined interface service stub is different from the return value stored in the database by the interface service stub, the return value corresponding to the interface address in the database needs to be updated to the target return value, i.e., the defined return value.
Step S308: and reading a return value corresponding to the interface address in the database and the calling mode.
In step S308, since the interface address is known, the return value and the calling mode corresponding to the interface address can be found in the database through the interface address.
Step S309: and completing the calling of the interface service stub based on the return value and the calling mode.
In step S309, since the interface address, and the calling method and the return value corresponding to the interface address are all obtained, the calling of the interface service stub can be completed through the interface address, the calling method, and the return value.
The method comprises the steps that interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub; if yes, determining that the return value of the interface service stub is a target return value, and updating the return value corresponding to the interface address in the database to be the target return value; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile, and analyzing the occupier based on pathVariable to obtain the interface address; reading a return value corresponding to the interface address in the database and the calling mode; and completing the calling of the interface service stub based on the return value and the calling mode. By the interface service pile processing method, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, the program does not need to be written again at the calling party, and the calling efficiency is improved.
Referring to fig. 4, for another interface service stub processing method disclosed in the embodiment of the present application, the interface service stub processing method specifically includes the following steps:
step S401: interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values.
Step S402: searching whether an interface address of the interface service stub exists in a database, and if the interface address of the interface service stub does not exist in the database, executing a step S403; if the interface address of the interface service stub exists in the database, step S407 is executed.
It should be noted that the execution principle and the specific execution process of step S401 and step S402 are the same as the execution principle and the specific execution process of step S101 and step S102 shown in fig. 1, and reference may be made to the above corresponding description, which is not described again here.
Step S403: and judging whether the quantity of the interface information stored in the database reaches a preset value, if so, executing a step S404, and if not, executing a step S405.
In step S403, the storage space of the database needs to be monitored because the storage space of the database is limited, and when the interface address of the defined interface service stub does not exist in the database, it indicates that the interface service stub needs to be newly built in the database, and before the interface service stub is newly built, it needs to ensure that there is enough space in the database to store the defined interface service stub, so that it is determined whether the amount of the interface information stored in the database reaches a preset value.
Step S404: and deleting old interface information currently stored in the database.
In step S404, when the number of the interface information corresponding to the interface service stub stored in the database reaches the preset value, the database cannot store more interface information corresponding to the interface service stub, and therefore, the old interface information currently stored in the database needs to be deleted first.
It should be noted that, because the storage capacity of the database is limited, when the interface information of the interface service stub stored in the database reaches a preset value, the interface information of a part of the interface service stubs stored in the database may also be deleted.
In a specific implementation, the storage time of all interface service stubs in the database may be obtained first, and the interface information of the N interface service stubs with the longest storage time may be deleted.
It should be further noted that, by acquiring the use frequency of each interface service stub in the database, the interface information of the interface service stub with the lowest use frequency may be deleted.
Step S405: and storing the interface information of the interface service stub into the database.
In step S405, the interface information of the interface service stub is stored in the database, that is, the interface address, the calling mode, and the return value of the interface service stub are created.
Step S406: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
Step S407: and determining that the return value of the interface service stub is a target return value, and updating the return value corresponding to the interface address in the database to be the target return value.
Step S408: and mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub.
Step S409: and resolving the occupation character based on the pathVariable to obtain the interface address.
Step S410: and reading a return value and a calling mode corresponding to the interface address in the database.
Step S411: and completing the calling of the interface service stub based on the return value and the calling mode.
It should be noted that the execution principle and the specific execution process of steps S406 to S411 are the same as the execution principle and the specific execution process of steps S304 to S309 shown in fig. 3, and reference may be made to the above corresponding description, which is not repeated herein.
The method comprises the steps that interface service piles and interface information of the interface service piles are defined, wherein the interface information comprises interface addresses, calling modes and return values; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub; and if so, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub. By the interface service pile processing method, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, the program does not need to be written again at the calling party, and the calling efficiency is improved.
Corresponding to the processing method of the interface service stub disclosed in the embodiment of the present invention, the embodiment of the present invention discloses a processing system of the interface service stub, and as shown in fig. 5, the processing system of the interface service stub includes:
a maintenance device 501, configured to define an interface service stub and interface information of the interface service stub, where the interface information includes an interface address, a calling manner, and a return value; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; if the identifier exists, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile;
the interface publishing device 502 is configured to map the interface address binding occupier based on pathVariable, and complete publishing of the interface service stub.
Preferably, the maintaining device 501 is further configured to determine that the return value of the interface service stub is a target return value, and update the return value corresponding to the interface address in the database to the target return value.
Preferably, the interface issuing device 502 is further configured to parse the occupation symbol to obtain the interface address based on the pathVariable; reading a return value corresponding to the interface address in the database and the calling mode; and completing the calling of the interface service stub based on the return value and the calling mode.
Preferably, the maintenance device 501 is further configured to determine whether the number of interface information stored in the database reaches a preset value; and if the quantity of the interface information stored in the database reaches a preset value, deleting the old interface information currently stored in the database.
The specific principle and the implementation process of the maintenance device 501 and the interface publishing device 502 in the processing system of the interface service stub disclosed in the embodiment of the present invention are the same as the processing method of the interface service stub disclosed in the embodiment of the present invention, and reference may be made to corresponding parts in the processing method of the interface service stub disclosed in the embodiment of the present invention, which are not described herein again.
The method comprises the steps that an interface service pile and interface information of the interface service pile are defined through a maintenance device, wherein the interface information comprises an interface address, a calling mode and a return value; searching whether an interface address of the interface service stub exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; if the identifier exists, mapping the interface address binding occupier based on pathVariable to complete the release of the interface service pile; and the interface issuing device maps the interface address binding occupier based on pathVariable to complete the issuing of the interface service stub. Through the processing system of the interface service pile, the interface address of the defined interface service pile is inquired in the database, if the interface address of the defined interface service pile is not inquired in the database, the interface service pile is newly built in the database and the newly built interface service pile is issued, and if the interface address of the defined interface service pile is inquired in the database, the return value of the interface address in the database is updated and issued, so that when a calling party calls the return value in the database, a program does not need to be written again at the calling party, and the calling efficiency is improved.
All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (4)
1. A processing method of an interface service stub is characterized by comprising the following steps:
defining an interface service pile and interface information of the interface service pile, wherein the interface information comprises an interface address, a calling mode and a return value;
searching whether an interface address of the interface service stub exists in a database;
if the interface service pile does not exist, storing the interface information of the interface service pile into the database;
mapping the interface address binding occupier based on pathVariable to complete the release of the interface service stub;
if the target return value exists, determining that the return value of the interface service stub is the target return value, updating the return value corresponding to the interface address in the database to the target return value, mapping the interface address binding occupier based on pathVariable, and completing the release of the interface service stub;
resolving the occupation symbol based on the pathVariable to obtain the interface address;
reading a return value corresponding to the interface address in the database and the calling mode;
and completing the calling of the interface service stub based on the return value and the calling mode.
2. The method of claim 1, wherein prior to storing the interface information of the interface service stub in the database, further comprising:
judging whether the quantity of the interface information stored in the database reaches a preset value or not;
and if the quantity of the interface information stored in the database reaches a preset value, deleting the old interface information currently stored in the database.
3. A system for processing an interface service stub, comprising:
the maintenance device is used for defining an interface service stub and interface information of the interface service stub, wherein the interface information comprises an interface address, a calling mode and a return value; searching whether an interface address of the interface service pile exists in a database; if the interface service pile does not exist, storing the interface information of the interface service pile into the database; if the target return value exists, determining that the return value of the interface service stub is the target return value, updating the return value corresponding to the interface address in the database to the target return value, mapping the interface address binding occupier based on pathVariable, and completing the release of the interface service stub;
the interface issuing device is used for mapping the interface address binding occupier based on the pathVariable, completing the issuing of the interface service stub, and analyzing the occupier based on the pathVariable to obtain the interface address; reading a return value corresponding to the interface address in the database and the calling mode; and completing the calling of the interface service stub based on the return value and the calling mode.
4. The system of claim 3,
the maintenance device is also used for judging whether the quantity of the interface information stored in the database reaches a preset value; and if the quantity of the interface information stored in the database reaches a preset value, deleting the old interface information currently stored in the database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910815217.0A CN110704132B (en) | 2019-08-30 | 2019-08-30 | Processing method and system of interface service pile |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910815217.0A CN110704132B (en) | 2019-08-30 | 2019-08-30 | Processing method and system of interface service pile |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110704132A CN110704132A (en) | 2020-01-17 |
| CN110704132B true CN110704132B (en) | 2022-06-17 |
Family
ID=69193795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910815217.0A Active CN110704132B (en) | 2019-08-30 | 2019-08-30 | Processing method and system of interface service pile |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704132B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20010087997A (en) * | 2000-03-09 | 2001-09-26 | 조진영 | Dynamic Bus Allocation Method and System for Multipoint Network using Variable Multipath |
| CN105096453A (en) * | 2015-05-15 | 2015-11-25 | 西安九智信管理咨询有限公司 | A modular outdoor intelligent service stub |
| CN106385437A (en) * | 2016-08-31 | 2017-02-08 | 广州唯品会信息科技有限公司 | Cluster selecting method and device |
| CN108985533A (en) * | 2017-06-02 | 2018-12-11 | 四川理工学院 | A kind of exercise management system and method based on Android platform |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7747451B2 (en) * | 2004-12-16 | 2010-06-29 | International Business Machines Corporation | Dynamic grid paths |
-
2019
- 2019-08-30 CN CN201910815217.0A patent/CN110704132B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20010087997A (en) * | 2000-03-09 | 2001-09-26 | 조진영 | Dynamic Bus Allocation Method and System for Multipoint Network using Variable Multipath |
| CN105096453A (en) * | 2015-05-15 | 2015-11-25 | 西安九智信管理咨询有限公司 | A modular outdoor intelligent service stub |
| CN106385437A (en) * | 2016-08-31 | 2017-02-08 | 广州唯品会信息科技有限公司 | Cluster selecting method and device |
| CN108985533A (en) * | 2017-06-02 | 2018-12-11 | 四川理工学院 | A kind of exercise management system and method based on Android platform |
Non-Patent Citations (2)
| Title |
|---|
| 基于Spring MVC的实习管理系统设计与实现;何桂兰;《科学咨询(科技.管理)》;20150103(第01期);29-30 * |
| 基于自匹配数据融合模型的城市交通路况诱导系统;农昭光;《信息技术》;20181130;148-152 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110704132A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110956269A (en) | Data model generation method, device, equipment and computer storage medium | |
| CN110825395A (en) | Multi-plug-in layered deployment system, device and medium | |
| CN112182089A (en) | Report generation method, device and equipment based on data warehouse model | |
| CN115129257A (en) | Data reading and writing method, electronic equipment and computer readable storage medium | |
| CN110704132B (en) | Processing method and system of interface service pile | |
| CN112215864B (en) | Contour processing method and device of electronic map and electronic equipment | |
| CN111026613A (en) | Log processing method and device | |
| CN115809200A (en) | Method and device for calling UI (user interface) automatic use case based on python | |
| CN114997111A (en) | Service processing method, device, computer equipment and storage medium | |
| CN113076086B (en) | Metadata management system and method for modeling model object using the same | |
| CN114936198A (en) | Data migration method and device | |
| CN114756261A (en) | Container cluster upgrading method and system, electronic equipment and medium | |
| CN113485761A (en) | Processing method, device, equipment and medium for resource access request | |
| CN114448972A (en) | Distributed storage log compression downloading method, system, terminal and storage medium | |
| CN114416163A (en) | Product management method, system, storage medium and electronic equipment | |
| CN114064678A (en) | Event data processing method and device and terminal equipment | |
| CN113110846A (en) | Method and device for acquiring environment variable | |
| CN112527276A (en) | Data updating method and device in visual programming tool and terminal equipment | |
| CN111125593A (en) | Block chain-based family tree information processing method and device and storage medium | |
| CN113055500B (en) | Address request method, device and computer readable storage medium | |
| CN113434468B (en) | File storage method, device, equipment and readable storage medium | |
| CN115237875B (en) | Log data processing method, device, equipment and storage medium | |
| CN114416552A (en) | Unit testing method, unit testing device, electronic equipment and storage medium | |
| CN115374122A (en) | Rollback data migration method, apparatus, device and medium of rollback table space | |
| CN118550597A (en) | Data processing method and device of service development component and electronic equipment |
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 |