CN113821557B - Method for carrying out data interaction between Web page and back end - Google Patents
Method for carrying out data interaction between Web page and back end Download PDFInfo
- Publication number
- CN113821557B CN113821557B CN202111120513.2A CN202111120513A CN113821557B CN 113821557 B CN113821557 B CN 113821557B CN 202111120513 A CN202111120513 A CN 202111120513A CN 113821557 B CN113821557 B CN 113821557B
- Authority
- CN
- China
- Prior art keywords
- request
- ajax
- xml file
- sql
- ajax request
- 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
- 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
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- 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
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for carrying out data interaction between a Web page and a back end, which comprises the following steps: A. setting a processing module for receiving a front-end AJAX request; B. configuring SQL sentences required to be executed by each AJAX request in an xml file, and setting an ID for each SQL sentence; C. the front end initiates an AJAX request to the rear end through the processing module, and the rear end finds out a corresponding target SQL statement in the xml file according to the ID of the SQL statement in the request, executes the target SQL statement and returns a response result. The invention unifies a large number of front-end and back-end interactive processing logics into a common step, does not need a developer to rewrite the front-end and back-end interactive processing logics, can complete front-end and back-end request processing only through simple HTML development and SQL sentence configuration, greatly improves development efficiency and effectively avoids code redundancy in a program.
Description
Technical Field
The invention relates to a data processing method, in particular to a method for carrying out data interaction between a Web page and a back end.
Background
AJAX refers to a web page development technique that creates interactive, fast dynamic web page applications that can update portions of the content in a web page without reloading the entire web page. AJAX can enable asynchronous updating of web pages by performing a small amount of data exchange with a server in the background.
As the service requirements increase in application systems, the data of the service requirements are increasingly huge, and database tables to be maintained are also increasingly more and more, so that the service data need to be managed and maintained through interaction between the front end and the back end. In the process of realizing the management of the data, the front-end page performs the operations of adding, deleting, modifying and inquiring the business data, wherein the operations directly correspond to the operations of adding, deleting and inquiring the database by the back-end program.
In the existing scheme that the front end and the back end interact, the front end adopts an AJAX request, and the back end adopts layering treatment. In the process that the front end initiates a request to the back end, the front end needs to submit the data of the form to the back end program through an AJAX request. The back-end program receives the front-end AJAX request, matches the front-end AJAX request to a corresponding interface according to url of the request, processes data in the interface, executes a corresponding SQL sentence, and finally returns an interface processing result to the front-end. In this process, if the front end needs to process a plurality of services interacted with the back end, a plurality of AJAX requests need to be written to call corresponding service processing interfaces of the back end to process corresponding service requests, AJAX sentences which need to interact with the database are executed by the service processing interfaces, and finally processed data are returned to the front end.
Disadvantages of the prior art: the back end is generally developed in a layered manner and is divided into a display layer, a business logic layer and a data persistence layer, and each request needs to write a large amount of repeated program codes, so that the workload of development is increased, and meanwhile, the time cost and the labor cost of code maintenance are also increased. When different parts of codes are written by different people, the difficulty of later maintenance is increased due to different writing habits and styles of each person.
Disclosure of Invention
The invention provides a method for carrying out data interaction between a Web page and a back end, which unifies a large number of processing logics interacted between the front end and the back end into a common execution step, and does not need a developer to write the processing logics interacted between the front end and the back end, so as to solve the problem of low efficiency in the development process and avoid the problem of code redundancy in application.
The method for carrying out data interaction between the Web page and the back end comprises the following steps:
A. setting a processing module for receiving front-end AJAX requests, wherein all the front-end AJAX requests needing to interact with the back-end call the processing module uniformly;
B. configuring SQL sentences required to be executed by each AJAX request in an xml file according to a set format, and setting a globally unique ID for each SQL sentence in the xml file;
C. and the processor at the front end initiates an AJAX request to the rear end through the processing module, and the processor at the rear end finds a corresponding target SQL statement in the xml file according to the ID of the SQL statement in the received AJAX request, executes the target SQL statement and returns a response result.
The invention only needs a unified back-end interface, namely the processing module, and does not need to develop a matched interface for each AJAX request, thereby reducing a large number of redundant and repeated processes, greatly improving the development efficiency, enabling a developer to complete the call of the AJAX request by only developing the front end view and the ID of the SQL executed by the configured front end view, greatly simplifying the complexity of codes and enabling the codes to be easier to maintain.
Preferably, in step B, after the xml file is configured, the xml file is automatically loaded into the system cache when the system is started. Therefore, the reading efficiency of xml files and SQL sentences can be obviously improved.
Preferably, in order to ensure the correctness of the SQL statement, an examination condition for examining the logic of the SQL statement before executing the SQL statement is configured in the xml file in step B, and is used for examining the grammar and logic of the SQL statement.
Specifically, in the step C, the front-end processor initiates an AJAX request to the back-end through the processing module, and the first method is that the front-end framework scans whether data needing to be automatically loaded exist in a page when the page is loaded, if so, the front-end framework constructs an AJAX request of the front-end and automatically initiates the AJAX request to the back-end; the second is to manually trigger the front-end AJAX request, and the user triggers the front-end framework to initiate an AJAX request by clicking a button on the page. These two subsequent processing logics that initiate the AJAX request are identical: the sent AJAX request specifies the ID of the SQL statement that needs to be executed, and if not, it will suggest that the ID is not bound. Because the sent AJAX request is processed by the unified processing module, the address of the request is not required to be specified when the request is initiated, and the program automatically specifies the address of the request. The front end initiates a request to the back end handler in two ways.
Specifically, in step C, after the processor at the back end receives the AJAX request, the executing steps include:
C1. the processor at the back end divides the request into a read request or a write request according to parameters carried in the received AJAX request, and respectively processes the read request and the write request through two independent processing logics, if the request is the read request, the AJAX request is distributed to a read processing interface, and if the request is the write request, the AJAX request is distributed to a write processing interface;
C2. after receiving the AJAX request, the read processing interface or the write processing interface judges whether the parameters carried in the AJAX request are empty, if so, the parameters are removed, then judges whether the parameters carried in the AJAX request carry the ID of the SQL statement to be executed, if not, an error code and error information are returned, otherwise, the parameters and the ID of the SQL statement to be executed are added into a set, and the set is transmitted to the SQL execution function;
the SQL executing function obtains the xml file, finds a corresponding target SQL sentence in the xml file through the ID of the SQL sentence to be executed, calls a database query executor to execute the target SQL sentence if the read processing interface processes, and calls a database update executor to execute the target SQL sentence if the write processing interface processes;
C4. after the target SQL statement is executed, if the return value exists, the return value is packaged and returned to the front end, the front end analyzes the returned parameters, the returned parameters are rendered to the view, and then the corresponding data are displayed on the front end page.
Further, in step C3, when the read processing interface invokes the database query executor to execute the target SQL statement, it is determined whether the AJAX request carries a parameter of the paging query, and if so, the paging query statement is spliced for the target SQL statement. By judging whether the paging query parameters exist, the returned data meets the front-end requirements, and the paging query is also more beneficial to checking the data.
Specifically, in step C, after the corresponding target SQL statement is found in the xml file, whether the target SQL statement passes or not is checked according to the checking condition, if the checking condition does not pass, the reason for the failing checking is returned, and if the checking condition passes, the target SQL statement is executed again and a response result is returned. The SQL statement is checked by the checking condition, so that errors in execution can be reduced, and the errors of the SQL statement can be found in time.
The invention integrates the AJAX request processing interfaces of the front end and the back end, adopts the unified processing module to automatically process the front-back end interaction requests, unifies a large number of front-end and back-end interaction processing logics into a common step, does not need a developer to re-write the front-end and back-end interaction processing logics, can complete the front-end and back-end request processing only through simple HTML development and SQL sentence configuration, greatly improves the development efficiency and effectively avoids code redundancy in a program.
The foregoing of the invention will be described in further detail with reference to the following detailed description of the examples. It should not be understood that the scope of the above subject matter of the present invention is limited to the following examples only. Various substitutions and alterations are also possible, without departing from the spirit of the invention, and are intended to be within the scope of the invention.
Drawings
FIG. 1 is a flow chart of a method for data interaction between a Web page and a backend of the present invention.
Detailed Description
The method for carrying out data interaction between the Web page and the back end shown in FIG. 1 comprises the following steps:
A. setting a processing module for receiving the front-end AJAX requests, and uniformly calling the processing module by all the front-end AJAX requests needing to interact with the back-end. The same processing module is called by different AJAX requests, so that the development of the front end does not need to write different javascript codes for each AJAX request, and the development process is greatly simplified;
B. configuring SQL sentences required to be executed by each AJAX request in an xml file according to a set format, and setting a globally unique ID for each SQL sentence in the xml file;
C. and the processor at the front end initiates an AJAX request to the rear end through the processing module, and the processor at the rear end finds a corresponding target SQL statement in the xml file according to the ID of the SQL statement in the received AJAX request, executes the target SQL statement and returns a response result.
The invention only needs a unified back-end interface, namely the processing module, and does not need to develop a matched interface for each AJAX request, thereby reducing a large number of redundant and repeated processes, greatly improving the development efficiency, enabling a developer to complete the call of the AJAX request by only developing the front end view and the ID of the SQL executed by the configured front end view, greatly simplifying the complexity of codes and enabling the codes to be easier to maintain.
On the basis of the scheme, in the step B, after the xml file is configured, the xml file is automatically loaded into a system cache when the system is started. Therefore, the reading efficiency of xml files and SQL sentences can be obviously improved. Meanwhile, in order to ensure the correctness of the SQL statement, the xml file is configured with checking conditions for checking the SQL statement logic before executing the SQL statement, and the checking conditions are used for checking the grammar and logic of the SQL statement. When the check condition is configured, the logic of the check is executed before the SQL is executed, and if the check is passed, the configured SQL statement is executed.
The front-end processor in the step C initiates an AJAX request to the rear end through the processing module, wherein the first mode is that the front-end framework scans whether data needing automatic loading exist in a page when the page is loaded, if so, the front-end framework constructs the front-end AJAX request and automatically initiates the request to the rear end; the second is to manually trigger the front-end AJAX request, and the user triggers the front-end framework to initiate an AJAX request by clicking a button on the page. These two subsequent processing logics that initiate the AJAX request are identical: the sent AJAX request specifies the ID of the SQL statement that needs to be executed, and if not, it will suggest that the ID is not bound. Because the sent AJAX request is processed by the unified processing module, the address of the request is not required to be specified when the request is initiated, and the program automatically specifies the address of the request. The front end initiates a request to the back end handler in two different ways.
When the processor at the back end receives the AJAX request, the specific steps are executed:
C1. the processor at the back end divides the request into a read request or a write request according to parameters carried in the received AJAX request, and respectively processes the read request and the write request through two independent processing logics, if the request is the read request, the AJAX request is distributed to a read processing interface, and if the request is the write request, the AJAX request is distributed to a write processing interface;
C2. after receiving the AJAX request, the read processing interface or the write processing interface judges whether the parameters carried in the AJAX request are empty, if so, the parameters are removed, then judges whether the parameters carried in the AJAX request carry the ID of the SQL statement to be executed, if not, an error code and error information are returned, otherwise, the parameters and the ID of the SQL statement to be executed are added into a set, and the set is transmitted to the SQL execution function;
and C3, the SQL executing function acquires the xml file, finds a corresponding target SQL sentence in the xml file through the ID of the SQL sentence to be executed, then checks whether the target SQL sentence passes or not according to the checking condition, returns a reason for checking failing if the checking fails, and executes the target SQL sentence and returns a response result if the checking passes. The SQL statement is checked by the checking condition, so that errors in execution can be reduced, and the errors of the SQL statement can be found in time. After the checking is passed, if the SQL statement corresponds to the read processing interface processing, the database query executor is called to execute the target SQL statement, whether the AJAX request carries the parameters of the paging query or not is judged, and if yes, the paging query statement is spliced for the target SQL statement. If the SQL statement corresponds to the write processing interface processing, a database update executor is called to execute the target SQL statement;
C4. after the target SQL statement is executed, if the return value exists, the return value is packaged and returned to the front end, the front end analyzes the returned parameters, the returned parameters are rendered to the view, and then the corresponding data are displayed on the front end page.
The invention processes the front-end Web request by the unified processing module through the configuration management SQL sentence, realizes the interaction of front/back ends, greatly reduces the workload of developers, greatly improves the development efficiency, and greatly facilitates the subsequent project iteration and the later code maintenance.
Claims (6)
- A method for carrying out data interaction between a Web page and a back end is characterized by comprising the following steps:A. setting a processing module for receiving front-end AJAX requests, wherein all the front-end AJAX requests needing to interact with the back-end call the processing module uniformly;B. configuring SQL sentences required to be executed by each AJAX request in an xml file according to a set format, and setting a globally unique ID for each SQL sentence in the xml file;C. the processor at the front end initiates an AJAX request to the rear end through the processing module, and the processor at the rear end finds a corresponding target SQL statement in the xml file according to the ID of the SQL statement in the received AJAX request, executes the target SQL statement and returns a response result; after the processor at the back end receives the AJAX request, the execution steps include:the method comprises the steps that C1, a processor at the back end divides a received AJAX request into a read request or a write request according to parameters carried in the request, the read request and the write request are respectively processed through two independent processing logics, if the request is the read request, the AJAX request is distributed to a read processing interface, and if the request is the write request, the AJAX request is distributed to a write processing interface;c2, after the reading processing interface or the writing processing interface receives the AJAX request, judging whether the parameter carried in the AJAX request is empty, if so, rejecting the parameter, and then judging whether the parameter carried in the AJAX request carries an ID of an SQL statement to be executed, if not, returning an error code and error information, otherwise, adding the parameter and the ID of the SQL statement to be executed into a set, and transmitting the set to an SQL execution function;c3, the SQL executing function acquires the xml file, finds a corresponding target SQL sentence in the xml file through the ID of the SQL sentence to be executed, calls a database query executor to execute the target SQL sentence if the read processing interface processes the target SQL sentence, and calls a database update executor to execute the target SQL sentence if the read processing interface processes the target SQL sentence;and C4, after the target SQL sentence is executed, if the return value exists, packaging the return value, returning the return value to the front end, analyzing the returned parameters by the front end, rendering the returned parameters to the view, and displaying the corresponding data on the front end page.
- 2. The method for data interaction between the Web page and the back end according to claim 1, wherein the method comprises the following steps: in the step B, after the xml file is configured, the xml file is automatically loaded into a system cache when the system is started.
- 3. The method for data interaction between the Web page and the back end according to claim 1, wherein the method comprises the following steps: and B, configuring checking conditions for checking SQL statement logic before executing the SQL statement in the xml file in the step B.
- 4. The method for data interaction between the Web page and the back end according to claim 1, wherein the method comprises the following steps: the front-end processor in the step C initiates an AJAX request to the rear end through the processing module, wherein the first mode is that the front-end framework scans whether data needing automatic loading exist in a page when the page is loaded, if so, the front-end framework constructs the front-end AJAX request and automatically initiates the request to the rear end; the second is to manually trigger the front-end AJAX request, and the user triggers the front-end framework to initiate an AJAX request by clicking a button on the page.
- 5. The method for data interaction between the Web page and the back end according to claim 1, wherein the method comprises the following steps: in step C3, when the read processing interface calls the database query executor to execute the target SQL statement, it is determined whether the AJAX request carries the parameters of the paging query, and if yes, the paging query statement is spliced for the target SQL statement.
- 6. A method for data interaction between a Web page and a back end according to claim 3, wherein: in the step C, after the corresponding target SQL sentence is found in the xml file, whether the target SQL sentence passes or not is checked according to the checking condition, if the target SQL sentence does not pass, the reason for the failed checking is returned, and if the target SQL sentence passes, the target SQL sentence is executed and a response result is returned.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111120513.2A CN113821557B (en) | 2021-09-24 | 2021-09-24 | Method for carrying out data interaction between Web page and back end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111120513.2A CN113821557B (en) | 2021-09-24 | 2021-09-24 | Method for carrying out data interaction between Web page and back end |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113821557A CN113821557A (en) | 2021-12-21 |
| CN113821557B true CN113821557B (en) | 2023-06-13 |
Family
ID=78921237
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111120513.2A Active CN113821557B (en) | 2021-09-24 | 2021-09-24 | Method for carrying out data interaction between Web page and back end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113821557B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114416197A (en) * | 2021-12-28 | 2022-04-29 | 成都易达数安科技有限公司 | Development-free scripted configuration method of APP background interface based on xml |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102110110A (en) * | 2009-12-28 | 2011-06-29 | ***通信集团公司 | Method and device for data access based on SOA (Service-Oriented Architecture) |
| CN102521254A (en) * | 2011-11-17 | 2012-06-27 | 广东电网公司电力科学研究院 | Uniform access method of isomeric database |
| CN102571934A (en) * | 2011-12-22 | 2012-07-11 | 深圳华强电子交易网络有限公司 | WEB page data binding method |
| CN109753532A (en) * | 2018-12-26 | 2019-05-14 | 苏州宏软信息技术有限公司 | Interface service system and its implementation method for browser end access database |
| CN112328917A (en) * | 2020-11-04 | 2021-02-05 | 浪潮云信息技术股份公司 | SQL (structured query language) writing oriented method for generating http interface service and data display page |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8601016B2 (en) * | 2011-08-30 | 2013-12-03 | International Business Machines Corporation | Pre-generation of structured query language (SQL) from application programming interface (API) defined query systems |
-
2021
- 2021-09-24 CN CN202111120513.2A patent/CN113821557B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102110110A (en) * | 2009-12-28 | 2011-06-29 | ***通信集团公司 | Method and device for data access based on SOA (Service-Oriented Architecture) |
| CN102521254A (en) * | 2011-11-17 | 2012-06-27 | 广东电网公司电力科学研究院 | Uniform access method of isomeric database |
| CN102571934A (en) * | 2011-12-22 | 2012-07-11 | 深圳华强电子交易网络有限公司 | WEB page data binding method |
| CN109753532A (en) * | 2018-12-26 | 2019-05-14 | 苏州宏软信息技术有限公司 | Interface service system and its implementation method for browser end access database |
| CN112328917A (en) * | 2020-11-04 | 2021-02-05 | 浪潮云信息技术股份公司 | SQL (structured query language) writing oriented method for generating http interface service and data display page |
Non-Patent Citations (2)
| Title |
|---|
| 基于Ajax4jsf的XML设计器;许琦;;计算机***应用(第01期);208-212 * |
| 基于富客户端的门户网站的开发与设计;张艺宝;中国优秀硕士学位论文全文数据库信息科技辑(第10期);I139-427 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113821557A (en) | 2021-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7996816B2 (en) | Method and apparatus for dynamically binding service component implementations for specific unit test cases | |
| US8793240B2 (en) | Generation of machine code for a database statement by specialization of interpreter code | |
| RU2445682C2 (en) | Graph-oriented programming and implementation based on manufacturers | |
| US9471282B2 (en) | System and method for using annotations to automatically generate a framework for a custom javaserver faces (JSF) component | |
| US8458681B1 (en) | Method and system for optimizing the object code of a program | |
| CN110502212B (en) | Multi-language-oriented high concurrency online development supporting method | |
| US20190018758A1 (en) | Using Emulation to Disassociate Verification from Stimulus in Functional Test | |
| US8429632B1 (en) | Method and system for debugging merged functions within a program | |
| US20070198705A1 (en) | System and method for integrating resources in a network | |
| US10466985B2 (en) | Hybrid deoptimization mechanism for class hierarchy analysis | |
| US8458651B2 (en) | Seamless migration of tuxedo® applications to a CICS® hosting environment | |
| CN111026634A (en) | Interface automation test system, method, device and storage medium | |
| US20140344781A1 (en) | Markup Language Integration at Runtime | |
| CN108664247B (en) | Page template data interaction method and device | |
| CN113821557B (en) | Method for carrying out data interaction between Web page and back end | |
| US20060129985A1 (en) | Development and execution platform | |
| CN112948610B (en) | Method and system for verifying result behaviors of graph query language | |
| CN109542464A (en) | Development deployment system, method and the storage medium of IoT equipment shell script | |
| US9507567B2 (en) | Facilitating use of techniques implemented by external library functions in process definitions of analytical applications | |
| US11429358B2 (en) | Representing asynchronous state machine in intermediate code | |
| CN114911541A (en) | Configuration information processing method and device, electronic equipment and storage medium | |
| CN113835690A (en) | Read-write separation multi-data source component and working method thereof | |
| CN116541015B (en) | Back-end storage method, device, server and storage medium | |
| CN117354114B (en) | Data service release method and system based on cloud native architecture | |
| US8056063B2 (en) | Method and apparatus minimizing code duplication in a statically typeable language program |
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 |