Method and device for unified mapping of http requests

Abstract

A method of collectively mapping a hypertext transfer protocol (HTTP) request and a device utilizing the same. The method comprises: separating configuration content from service logic content by acquiring a mapping file for accessing to a third party HTTP service; associating the mapping file with an interface; generating a JAVA object corresponding to the mapping file; generating, according to a reflection proxy annotation corresponding to the associated interface called by a request, a dynamic proxy object; when processing a HTTP request, processing, by the dynamic proxy object, according to the JAVA object generated by the mapping file, the request, calling, by the dynamic proxy object, a method in an HTTP request basic service, and completing, by the dynamic proxy object, the HTTP request. As a result, the mapping file can be generated only once and used for a plurality of times, thereby realizing a HTTP request call while reducing development difficulty and increasing a reuse rate.

Description

technical field [0001] The present application relates to the computer field, and in particular to a technique for uniformly mapping HTTP requests. Background technique [0002] Nowadays, many JAVA back-end applications need to call the interface of the third-party application through HTTP (HTTP, HyperText Transfer Protocol, network protocol), so the code written must have the URL (UniformResource Locator, Uniform Resource Locator) and port of the HTTP request. and passed configuration parameters. [0003] When the backend of the existing JAVA (an object-oriented programming language that can write cross-platform application software) sends HTTP requests, different methods must be defined for invoking HTTP requests of different third-party applications according to different business logics. The logic inside is to assemble parameters and call the underlying HTTP common request method, which leads to code redundancy and duplication of development. Multiple URLs, ports, and ...

AI Technical Summary

Problems solved by technology

[0003] When the backend of the existing JAVA (an object-oriented programming language that can write cross-platform application software) sends HTTP requests, different methods must be defined for invoking HTTP requests of different third-party applications according to different business logics. The logic inside is to assemble parameters and call the underlying HTTP common request method, which leads to code redundancy and duplication of development

Multiple URLs, ports, and configuration parameters for calling third parties will be defined in the code, resulting in the mixing of business logic code and request configuration parameter code, which is not well separated, and different developers continue to repeat according to the business Develop the basic code for accessing HTTP requests, resulting in a low code reuse rate and a decline in development efficiency

Images