CN112947984B

CN112947984B - Application program development method and device

Info

Publication number: CN112947984B
Application number: CN202011051343.2A
Authority: CN
Inventors: 李高飞
Original assignee: Shenzhen Mingyuan Cloud Technology Co Ltd
Current assignee: Shenzhen Mingyuan Cloud Technology Co Ltd
Priority date: 2020-09-29
Filing date: 2020-09-29
Publication date: 2024-05-14
Anticipated expiration: 2040-09-29
Also published as: CN112947984A

Abstract

The application is applicable to the technical field of computers, and provides an application program development method and device, wherein the method comprises the following steps: generating a page operation request for an application program to be developed; sending the page operation request to a server, so that the server determines API association information corresponding to a background API for responding to the page operation request; and developing the application program based on the API association information. Therefore, the page operation function can be accurately related to the corresponding API related information, the development and maintenance difficulty of service logic or application programs with complicated page operation functions is reduced, and the development efficiency is improved.

Description

Application program development method and device

Technical Field

The application belongs to the technical field of computers, and particularly relates to an application program development method and device.

Background

With the continued development of internet technology, some internet applications, such as ERP (ENTERPRISE RESOURCE PLANNING ) applications, are also increasingly becoming diversified and complex in integrated business logic.

However, the complexity of business logic increases the difficulty of developing or maintaining a client system during routine development or while troubleshooting client system problems.

In view of the above problems, currently, no preferred solution is proposed.

Disclosure of Invention

In view of this, the embodiments of the present application provide a method and an apparatus for developing an application program, so as to at least solve the problem in the prior art that an application program with complicated business logic is difficult to develop or maintain.

A first aspect of an embodiment of the present application provides an application development method, applied to a client, where the method includes: generating a page operation request for an application program to be developed; sending the page operation request to a server, so that the server determines API association information corresponding to a background API for responding to the page operation request; and developing the application program based on the API association information.

A second aspect of an embodiment of the present application provides an application development method, applied to a server, where the method includes: receiving a page operation request for an application program to be developed from a client; determining API-associated information corresponding to a background API for responding to the page operation request; and sending the API association information to the client so that the client develops the application program based on the API association information.

A third aspect of an embodiment of the present application provides an application development apparatus, including: a page operation request generation unit configured to generate a page operation request for an application program to be developed; a page operation request transmitting unit configured to transmit the page operation request to a server, so that the server determines API-associated information corresponding to a background API for responding to the page operation request; and the application program development unit is configured to develop the application program based on the API association information.

A fourth aspect of an embodiment of the present application provides an application development apparatus, including: a page operation request receiving unit configured to receive a page operation request for an application program to be developed from a client; an API-associated information determination unit configured to determine API-associated information corresponding to a background API for responding to the page operation request; and the API association information sending unit is configured to send the API association information to the client so that the client develops the application program based on the API association information.

A fifth aspect of the embodiments of the present application provides a mobile terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method as described above when executing the computer program.

A sixth aspect of the embodiments of the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method as described above.

A seventh aspect of the embodiments of the present application provides a computer program product for causing a mobile terminal to carry out the steps of the method as described above when the computer program product is run on the mobile terminal.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

According to the embodiment of the application, after the client sends the page operation request to the server, the server can feed back the API association information corresponding to the background API for responding to the page operation request to the client, so that the page operation function can be accurately associated with the corresponding API association information, the maintenance difficulty of service logic or an application program with complicated page operation function can be reduced, and the development efficiency can be improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 illustrates a flowchart of an example of an application development method according to an embodiment of the application;

FIG. 2 illustrates a flowchart of an example of an application development method according to an embodiment of the application;

FIG. 3 illustrates a flowchart of one example of determining API-associated information in accordance with an embodiment of the present application;

FIG. 4 illustrates an architectural diagram of an example of determining SQL statements associated with page functions according to an embodiment of the application;

FIG. 5 illustrates a flowchart of an example of developing an application based on API-associated information in accordance with an embodiment of the present application;

FIG. 6 illustrates an architecture diagram of an example of automatically generating customized extension code templates according to an embodiment of the application;

FIG. 7 illustrates a flowchart of an example of developing an application based on API-associated information in accordance with an embodiment of the present application;

FIG. 8 illustrates an architecture diagram of an example of automatically generating API manifest in accordance with an embodiment of the present application;

FIG. 9 shows a block diagram of an example of an application development device according to an embodiment of the application;

FIG. 10 shows a block diagram of an example of an application development device according to an embodiment of the application;

Fig. 11 is a schematic diagram of an example of a mobile terminal according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

In order to illustrate the technical scheme of the application, the following description is made by specific examples.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

In particular implementations, the mobile terminals described in embodiments of the application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). It should also be appreciated that in some embodiments, the above-described devices are not portable communication devices, but rather desktop computers having touch-sensitive surfaces (e.g., touch screen displays and/or touch pads).

In the following discussion, a mobile terminal including a display and a touch-sensitive surface is described. However, it should be understood that a mobile terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.

Various applications that may be executed on the mobile terminal may use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal may be adjusted and/or changed between applications and/or within the corresponding applications. In this way, the common physical architecture (e.g., touch-sensitive surface) of the terminal may support various applications with user interfaces that are intuitive and transparent to the user.

Fig. 1 shows a flowchart of an example of an application development method according to an embodiment of the present application. As to the execution subject of the embodiment of the present application, it may be a client, i.e., a terminal device that runs an application program to be developed (e.g., daily development or maintenance).

As shown in fig. 1, in step 110, a client generates a page operation request for an application to be developed (e.g., ERP). For example, the client may expose a corresponding page while running the application, at which time the user may request development or maintenance for certain functions on the page, and may perform corresponding operations (e.g., clicking on a control, etc.), thereby generating a corresponding page operation request.

In step 120, the client sends a page operation request to the server, so that the server determines API-associated information corresponding to a background API for responding to the page operation request. It should be noted that the API-associated information may represent various information associated with the API, such as API attribute information, information that the API can call, and the like, and different page operation requests may be matched with different types of API-associated information.

In step 130, the client develops the application based on the API-associated information. In one example of an embodiment of the present application, a development user may refer to API-associated information and perform further development operations on a client. In another example of an embodiment of the present application, the client may adaptively complete the corresponding development operation process using the API association information.

In the embodiment of the application, the client can obtain the API associated information corresponding to the page operation function through information interaction with the server, and a development user is not required to analyze or distinguish which information in the numerous application information is the API associated information corresponding to the page operation function.

Fig. 2 shows a flowchart of an example of an application development method according to an embodiment of the present application. As for the execution subject of the embodiment of the present application, it may be a server, that is, a server for providing services (including development services) for an application program.

As shown in fig. 2, in step 210, the server receives a page operation request for an application to be developed from a client.

In step 220, the server determines API-associated information corresponding to the background API for responding to the page operation request. The server may parse the information carried in the page operation request, find a background API according to the information, and obtain corresponding API association information.

In step 230, the server sends the API-related information to the client, so that the client develops the application based on the API-related information.

According to the embodiment of the application, the server can identify the API associated information corresponding to the page operation request, so that the maintenance difficulty of service logic or application programs with complicated page operation functions can be reduced, and the development efficiency can be improved.

In some cases, development users need to first know which database operations were performed during the business process and take it as a clue in the process of maintaining or secondarily developing the application. However, the existing SQL tracking tool in the industry can only track all SQL sentences executed by a certain database, and can not quickly identify which SQL is related to the current service function, so that a development user needs to reversely estimate the SQL sentences needing to pay attention according to the SQL content, thereby influencing the development efficiency.

In view of this, in some examples of embodiments of the application, the page operation request includes SQL trace identification information and, accordingly, the API-associated information includes SQL statements called by the background API. Therefore, the business function indicated by the page operation request can be directly associated with the corresponding SQL statement, reverse deduction by a development user is not needed, and development efficiency is improved.

FIG. 3 illustrates a flowchart of an example of determining API-associated information in accordance with an embodiment of the present application.

As shown in fig. 3, in step 310, the server parses the SQL trace identification information in the page operation request.

In step 320, the server extracts the SQL statement called by the background API based on the SQL trace identification information. For example, the SQL trace identifying information may function to trigger an SQL statement trace operation, such as enabling the SQL statement trace function of the server for the corresponding background API when the server recognizes that the request contains SQL trace identifying information.

In step 330, the server determines API-associated information based on the extracted SQL statement.

Through the embodiment of the application, the server can find each SQL statement associated with the page operation request by utilizing the SQL tracking operation, and clearly indicates which database operation is executed in the business process, so that the development efficiency can be effectively improved.

FIG. 4 illustrates an architectural diagram of an example of determining SQL statements associated with page functions according to an embodiment of the application.

As shown in fig. 4, a browser 411 and a Fiddler plug-in 413 are provided in the client 410, and a network processing module IIS site 421 and a database 423 are provided in the server 420. It should be noted that, when the background service code of the application program accesses the database, the platform bottom layer API needs to be called.

Specifically, IIS site 421 may be added in the application background (i.e., server 420) so that after the ERP site turns on the tracking function, all SQL statements accessed internally by the API are recorded as long as the page operation request can reach the background API. Further, when feeding back the results to the client, the application background may automatically put the recorded SQL statement into the HTTP return header. Accordingly, when the Fiddler plug-in recognizes that the return header contains SQL statements, it can display the SQL statements in the Fiddler. Preferably, not only the SQL statement but also the parameter value of the SQL query may be displayed.

Referring to the example in FIG. 4, after a development user operates browser 411, a corresponding page traffic may be generated, which may be intercepted by Fiddler plug-in 413. Further, fiddler plug-in 413 could place a special trace tag (i.e., SQL trace identification information) in the request header. The client 410 may then send a page operation request to the server 420.

After the server 420 receives the page operation request, SQL tracking may be initiated by setting a global variable based on the SQL tracking identification information contained in the request header. In this way, during execution of the service function code, all SQL statements that call the data access layer interface to access the database 423 can be recorded by the data access layer.

When the server 420 sends the feedback result, the recorded SQL sentence can be put into the return header information and returned to the Fiddler plug-in, so that the Fiddler plug-in obtains the return data of the server 420, obtains the SQL sentence from the request header information, displays the SQL sentence in the Fiddler tool interface, and puts together other tracking records of the current request, thereby facilitating the viewing of the development user.

According to the embodiment of the application, a development user can quickly position a certain page request by means of the SQL tracking function of the Fiddler plug-in tool, which business SQL sentences are executed in the background, the development user can be helped to accurately find out a certain page request, which business SQL is executed at the bottom in the background of the server, so that the problem of positioning codes can be debugged more quickly, the execution time of the tracked SQL can be displayed, and the quick positioning of SQL sentences with performance hidden troubles by developers is facilitated.

In addition, some SQL tracing tools used in the related art can only grasp SQL sentences executed by a database and cannot be associated with business function codes. However, in the embodiment of the application, the development and efficiency promotion tool based on Fiddler can effectively relate SQL executed by the function code to the function itself, so that the efficiency of function development is greatly improved.

In some cases, the development of applications can be categorized into two types of development, product and personalized customization. Here, custom developers can only extend based on product functionality and do not allow direct modification of product source code. Custom development users sometimes need to know the execution logic of the page function code and need to see the code execution logic behind the current page function.

When the expansion is needed based on the page function in the process of custom development, a custom development user needs to write an expansion method aiming at the page function, the codes of the expansion method meet certain format requirements, and when the expansion is performed each time, the custom development user needs to write partial codes which are the same as the requirements, so that the development efficiency is affected.

In view of this, in some examples of the embodiments of the present application, the API-associated information may include link information (i.e., URL) corresponding to a background API, and may be specific to a product API corresponding to a page operation request (or a current page request), and the client may automatically generate a custom extended "scaffold" code to improve development efficiency.

Fig. 5 shows a flowchart of an example of developing an application based on API association information according to an embodiment of the present application.

As shown in fig. 5, in step 510, the client determines a corresponding API service method and API class according to the link information corresponding to the background API. It should be noted that, the API requests corresponding to different classes or service methods in the server have corresponding URL format rules, so that the URL format rules may be used to determine the corresponding API service methods and API classes.

In step 520, the client determines a corresponding API extension code based on the API service method, the API class, and a format rule of a preset extension API.

In step 530, the client develops an application based on the API extension code.

In the embodiment of the application, based on the principle that the URL mode corresponding to the API request is fixed, the corresponding API class and method can be determined by utilizing the link information corresponding to the background API, and the corresponding scaffold code can be automatically expanded by using the preset format rule of the expansion API, so that the development efficiency can be improved, and the development cost can be reduced.

FIG. 6 illustrates an architecture diagram of an example of automatically generating customized extension code templates according to an embodiment of the application.

As shown in fig. 6, the server 620 may send a request URL corresponding to the background API to the client 610. Further, the Fiddler plug-in 613 can find the service method of the called API by parsing the request URL of the background API. In addition, aiming at the extension code of the background API, the writing method is required to meet a certain specification, so that the Fiddler can automatically generate an extended 'scaffold' code according to the currently called API method, thereby reducing the development cost.

Referring to the example in FIG. 6, the URL of the background API may be tracked by the Fiddler plug-in 613, automatically generating the "scaffolding" code for the extension API. Specifically, after the development user operates the browser 611, a corresponding page traffic may be generated, which may be intercepted by the Fiddler plug-in 613. The Fiddler plug-in 613 can then parse the request URL and determine the interface request corresponding to the back-end API, so that the Fiddler plug-in 613 can automatically parse the specific class and method name of the API request according to the format rule of the API request URL. Further, FIddler plug-in 613 may automatically generate an extended "scaffolding" code from the API class and extended method name, and the format rules of the extended API (or API extended code template).

Through the embodiment of the application, a custom development user can quickly obtain the 'scaffold' expansion code of a certain background API service interface, and can construct an expansion function more quickly.

In some cases, the application is a completely front-end and back-end separated architecture, the back-end opens services in the form of APIs to the front-end, and before expanding the product functions, the custom developer needs to know which API services have been opened by the product back-end, and then expand and develop the APIs.

In view of this, in some examples of the embodiments of the present application, the API related information may include link information (i.e., URL) corresponding to a background API, and when an application program is developed, the client may automatically grab the API class in which the client locates based on the link information corresponding to the background API, so that a development user may learn which related API interfaces are in the API class.

Fig. 7 shows a flowchart of an example of developing an application based on API association information according to an embodiment of the present application.

As shown in fig. 7, in step 710, the client determines an API class name corresponding to the background API based on the link information corresponding to the background API. As described above, since the link information of APIs of different classes respectively have corresponding fixed format rules, the API class to which the link information corresponds can be identified.

In step 720, the client determines an API manifest that matches the API class name.

In step 730, the client develops an application based on the API manifest.

Through the embodiment of the application, a developer can acquire the related API interfaces of the API classes corresponding to the current page at the client, so that a development user can conveniently and quickly find the required background API interface.

In some examples of embodiments of the application, not all API interfaces in an API class may be open in a server, e.g., only some of the API interfaces in an API class may be present in a server. Specifically, the client may send the API class name to the server so that the server gets an API manifest that matches the API class name. Further, the client may receive an API manifest from the server. Thus, the development user can intuitively know the interface in the API class related to the current operation page opened in the server through the client.

FIG. 8 illustrates an architecture diagram of an example of automatically generating API manifest according to an embodiment of the application.

As shown in fig. 8, the API list related to the current page can be quickly acquired based on the URL corresponding to the background API.

As described above, the filer plug-in 813 can identify the API service method and API class to which the background API corresponds. At this point Fiddler plug-in 813 can call a specialized interface, recognize internally through a "reflection mechanism" which APIs are still in the API class, and then return to Fidder tool and get the corresponding API list.

Referring to the example of FIG. 8, API request tracking may be performed by Fiddler plug-in 813 to automatically obtain a back-end API class-related API manifest.

Specifically, after a development user operates browser 811, a corresponding page traffic may be generated that may be intercepted by Fiddler plug-in 813. Further, server 820 may return a URL corresponding to the background API to the client. At this time, the Fiddler plug-in 813 can parse the URL, find it to be a back-end API interface class, then call the back-end fixed parse API interface, and pass the API interface class name. Server 820 may parse the API interface class name and obtain a list of all published API interface methods for the specified class, and include annotation text for each method, and return to Fiddler plug-in 813.

Preferably FIddler plug-in 813 also can display the published API manifest as a list for presentation to a development user.

The embodiment of the application can meet the daily development conditions of routine debugging, rapid expansion of custom APIs and the like, and improves the development efficiency.

Fig. 9 shows a block diagram of an example of an application development apparatus according to an embodiment of the present application.

As shown in fig. 9, the application development apparatus 900 includes a page operation request generation unit 910, a page operation request transmission unit 920, and an application development unit 930.

The page operation request generation unit 910 is configured to generate a page operation request for an application to be developed.

The page operation request transmitting unit 920 is configured to transmit the page operation request to a server so that the server determines API-associated information corresponding to a background API for responding to the page operation request.

The application development unit 930 is configured to develop the application based on the API-related information.

Fig. 10 shows a block diagram of an example of an application development apparatus according to an embodiment of the present application.

As shown in fig. 10, the application development device 1000 includes a page operation request receiving unit 1010, an API-associated information determining unit 1020, and an API-associated information transmitting unit 1030.

The page operation request receiving unit 1010 is configured to receive a page operation request for an application program to be developed from a client.

The API-associated information determining unit 1020 is configured to determine API-associated information corresponding to a background API for responding to the page operation request.

The API-related information transmitting unit 1030 is configured to transmit the API-related information to the client so that the client develops the application based on the API-related information.

It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.

Fig. 11 is a schematic diagram of an example of a mobile terminal according to an embodiment of the present application. As shown in fig. 11, the mobile terminal 1100 of this embodiment includes: a processor 1110, a memory 1120, and a computer program 1130 stored in the memory 1120 and executable on the processor 1110. The steps of the application development method embodiments described above, such as steps 110 through 130 shown in fig. 1, are implemented by the processor 1110 when executing the computer program 1130. Or the processor 1110, when executing the computer program 1130, performs the functions of the modules/units of the apparatus embodiments described above, e.g., the functions of the units 1010 through 1030 shown in fig. 10.

Illustratively, the computer program 1130 may be partitioned into one or more modules/units that are stored in the memory 1120 and executed by the processor 1110 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing particular functions in describing the execution of the computer program 1130 in the mobile terminal 1100. For example, the computer program 1130 may be divided into a page operation request receiving module, an API-associated information determining module, and an API-associated information transmitting module, each of which specifically functions as follows:

and the page operation request receiving module is configured to receive a page operation request for an application program to be developed from the client.

And an API-associated information determination module configured to determine API-associated information corresponding to a background API for responding to the page operation request.

And the API association information sending module is configured to send the API association information to the client so that the client develops the application program based on the API association information.

The mobile terminal 1100 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or other computing devices. The mobile terminal may include, but is not limited to, a processor 1110, a memory 1120. It will be appreciated by those skilled in the art that fig. 11 is merely an example of a mobile terminal 1100 and is not intended to limit the mobile terminal 1100, and may include more or fewer components than shown, or may combine certain components, or may include different components, such as an input-output device, a network access device, a bus, etc.

The Processor 1110 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 1120 may be an internal storage unit of the mobile terminal 1100, such as a hard disk or a memory of the mobile terminal 1100. The memory 1120 may also be an external storage device of the mobile terminal 1100, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like, which are provided on the mobile terminal 1100. Further, the memory 1120 may also include both internal storage units and external storage devices of the mobile terminal 1100. The memory 1120 is used to store the computer program and other programs and data required for the mobile terminal. The memory 1120 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. For specific working processes of the units and modules in the system, reference may be made to corresponding processes in the foregoing method embodiments.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the 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 application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/mobile terminal and method may be implemented in other manners. For example, the apparatus/mobile terminal embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown 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 units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The above units may be implemented in hardware or in software.

The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. An application program development method applied to a client, the method comprising:

When an application program is operated, displaying corresponding page operation on the page to generate a page operation request aiming at the application program to be developed;

Sending the page operation request to a server, so that the server determines API association information corresponding to a background API for responding to the page operation request;

developing the application program based on the API association information;

the page operation request comprises SQL tracking identification information, and correspondingly, the API association information comprises SQL sentences called by the background API, and the SQL tracking identification information is used for triggering SQL sentence tracking operation;

The API-associated information includes link information corresponding to the background API,

Wherein the developing the application program based on the API-related information includes:

Determining a corresponding API service method and an API class according to the link information corresponding to the background API;

Determining corresponding API extension codes based on the API service method, the API class and a preset format rule of an extension API;

Developing the application program based on the API extension code;

Or alternatively

Determining an API class name corresponding to the background API based on the link information corresponding to the background API;

Determining an API list matched with the API class name;

And developing the application program based on the API list.

2. The method of claim 1, wherein said determining an API manifest that matches the API class name comprises:

sending the API class name to the server so that the server obtains an API list matched with the API class name;

the API manifest is received from the server.

3. An application program development method applied to a server, the method comprising:

receiving a page operation request of an application program to be developed when the client displays a corresponding page to operate when the application program is operated from the client, wherein the page operation request comprises SQL tracking identification information;

Analyzing SQL tracking identification information in a page operation request, and determining API related information corresponding to a background API for responding to the page operation request, wherein the API related information comprises SQL statements called by the background API, and the SQL tracking identification information is used for triggering SQL statement tracking operation;

transmitting the API association information to the client so that the client develops the application program based on the API association information;

Developing the application program based on the API extension code;

Or alternatively

Determining an API list matched with the API class name;

And developing the application program based on the API list.

4. The method of claim 3, wherein the determining API-associated information corresponding to a background API for responding to the page operation request comprises:

Analyzing the link information corresponding to the background API;

And determining API association information based on the link information corresponding to the parsed background API.

5. An application development device, comprising:

The page operation request generation unit is configured to display corresponding page operations to generate page operation requests for the application programs to be developed when the application programs are operated;

A page operation request sending unit configured to send the page operation request to a server, so that the server determines API related information corresponding to a background API for responding to the page operation request, the page operation request including SQL tracking identification information, and correspondingly, the API related information including an SQL statement called by the background API, the SQL tracking identification information being used for triggering an SQL statement tracking operation;

An application development unit configured to develop the application based on the API-related information;

Developing the application program based on the API extension code;

Or alternatively

Determining an API list matched with the API class name;

And developing the application program based on the API list.

6. An application development device, comprising:

the page operation request receiving unit is configured to receive a page operation request of an application program to be developed when the client displays a corresponding page for operation when the application program is operated from the client, wherein the page operation request comprises SQL tracking identification information;

the system comprises an API association information determining unit, a page operation request processing unit and a page operation request processing unit, wherein the API association information determining unit is configured to analyze SQL trace identification information in the page operation request and determine API association information corresponding to a background API for responding to the page operation request, the API association information comprises SQL sentences called by the background API, and the SQL trace identification information is used for triggering SQL sentence trace operation;

an API-associated information transmitting unit configured to transmit the API-associated information to the client so that the client develops the application based on the API-associated information;

Developing the application program based on the API extension code;

Or alternatively

Determining an API list matched with the API class name;

And developing the application program based on the API list.