CN113114505B - httpClient-based access request processing method and system - Google Patents
httpClient-based access request processing method and system Download PDFInfo
- Publication number
- CN113114505B CN113114505B CN202110396882.8A CN202110396882A CN113114505B CN 113114505 B CN113114505 B CN 113114505B CN 202110396882 A CN202110396882 A CN 202110396882A CN 113114505 B CN113114505 B CN 113114505B
- Authority
- CN
- China
- Prior art keywords
- interface
- request
- hospital
- time
- overtime
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Health & Medical Sciences (AREA)
- Signal Processing (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Tourism & Hospitality (AREA)
- Computing Systems (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an httpClient-based access request processing method and system, wherein the method comprises the following steps: presetting corresponding httpClient for each preset overtime time; carrying out overtime time configuration with different dimensions by hospital id and uri interfaces according to service requirements in advance; receiving an interface request for accessing the hospital ERP system, analyzing a hospital id interface and a uri interface in the request according to the interface request, and determining timeout time configuration corresponding to the interface request according to an analysis result; determining the overtime of the request interface according to the overtime configuration corresponding to the interface request; loading a corresponding httpClient to call an interface according to the overtime of the request interface; and the httpClient fuses the interface according to the built-in timeout. The invention sets different overtime time configurations for different hospitals and different service interfaces according to service requirements to fuse the interfaces, thereby solving the problem that accurate overtime time cannot be set to cause service avalanche due to different system performances and network conditions of each hospital.
Description
Technical Field
The invention relates to the technical field of information processing, in particular to an httpClient-based access request processing method and system.
Background
In the era of mobile internet, mobile phones have become an indispensable tool for people. The intelligent hospital is a platform of the intelligent hospital which is created by relying on the communication and payment functions provided by WeChat and payment treasured and combining the industrial characteristics, can be used for user registration, inquiry, prescription, payment and the like, and solves the industrial pain points that patients in the existing hospital have long queuing time and occupy more hospital resources.
The intelligent hospital platform needs to be communicated with the hospital erp system in related functions such as registration, prescription and the like, and the related request interfaces have the condition of long response time due to related reasons such as performance of the hospital erp system and network. In order to ensure that the interface of each hospital can normally request, the scheme mainly adopted at present is to set an overtime of 120 seconds; however, due to the fact that the overtime time is long, when the hospital erp system is unstable, the current thread occupies, and therefore a great amount of thread resources are occupied; meanwhile, most services need to call an erp interface, so that the load of upstream service threads is collectively increased, and service avalanche is easy to occur.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides an httpparent-based access request processing method and system, which can ensure that overtime fusing can be carried out according to overtime time configuration when a hospital erp system has unstable service, protect system thread resources and prevent service failure spreading.
In order to achieve the aim, the invention discloses an httpparent-based access request processing method, which comprises the following steps:
step 1, setting corresponding httpClient for each preset timeout in advance;
step 2, carrying out overtime time configuration with different dimensions by hospital id and uri interfaces according to service requirements in advance;
step 3, receiving an interface request for accessing the hospital ERP system, analyzing a hospital id interface and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
step 4, determining the overtime of the request interface according to the overtime configuration corresponding to the interface request;
step 5, loading the corresponding httpClient to call the interface according to the overtime of the request interface;
and 6, fusing the interface according to the built-in overtime time by httpClient.
Further, step 4 comprises:
step 401, acquiring corresponding request time historical data within a preset time according to timeout time configuration corresponding to an interface request;
step 402, determining an average value of the request time historical data according to the request time historical data, wherein the average value is used as the timeout time of the request interface.
Further, in step 401, when the timeout time corresponding to the interface request is configured as the timeout time configuration of the total interfaces of the hospital, the request time history data is the request time history data of all interfaces of the hospital.
Further, in step 401, when the timeout time corresponding to the interface request is configured as the uri interface, the request time history data is the request time history data corresponding to the uri interface.
Further, in step 1, the step of performing timeout time configuration of different dimensions in advance by using hospital id and uri interfaces according to service requirements includes:
and carrying out overtime configuration on each hospital total interface by using each hospital id, and then carrying out overtime configuration on each uri interface under each hospital according to business needs, wherein the priority level of the overtime configuration of each uri interface is greater than that of the hospital total interface.
On the other hand, the invention also discloses an httpparent-based access request processing system, which comprises:
the initialization module is used for presetting corresponding httpClient for each preset timeout;
the overtime configuration module is used for carrying out overtime configuration with different dimensions in advance through hospital id and uri interfaces according to service requirements;
the http-center module is used for receiving an interface request for accessing the hospital ERP system, analyzing a hospital id and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
the overtime time determining module is used for determining the overtime time of the request interface according to the overtime time configuration corresponding to the interface request;
the httpClient calling module is used for loading the corresponding httpClient to carry out interface calling according to the overtime of the request interface;
and the httpClient fusing module is used for fusing the interface according to the built-in timeout time of the httpClient.
Further, the timeout time determining module includes:
the historical data acquisition unit is used for acquiring corresponding request time historical data within preset time according to the overtime configuration corresponding to the interface request;
and the overtime calculation unit is used for determining the average value of the request time historical data according to the request time historical data, and the average value is used as the overtime of the request interface.
Further, in the historical data obtaining unit, when the timeout period corresponding to the interface request is configured to the timeout period configuration of the total interface of the hospital, the request time historical data is the request time historical data of all interfaces of the hospital.
Further, in the history data obtaining unit, when the timeout time corresponding to the interface request is configured as the uri interface, the request time history data is the request time history data corresponding to the uri interface.
Further, the timeout period configuration module is specifically configured to perform timeout period configuration on each hospital total interface by using each hospital id, and then perform timeout period configuration on each uri interface under each hospital according to service needs, where a priority level of the timeout period configuration of each uri interface is greater than the timeout period configuration of the hospital total interface.
Compared with the prior art, the invention has the following advantages: according to the method, overtime configuration with different dimensions is carried out according to the hospital id and uri interfaces, when an interface request for accessing the hospital ERP system is received, the hospital id and uri interfaces in the request are analyzed according to the interface request to determine the overtime configuration corresponding to the interface request, so that the overtime corresponding to each interface is determined, and finally, corresponding httpClient is fused according to the overtime request, so that when the hospital ERP system is unstable in service, overtime fusing can be carried out according to the overtime of different interfaces, the thread resources of the system are protected, and the service failure is prevented from spreading.
The invention sets different overtime time configurations for different hospitals and different service interfaces according to service requirements to carry out interface fusing, thereby solving the problem that accurate overtime time cannot be set to cause service avalanche due to different system performances and network conditions of each hospital.
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, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the httpClient-based access request processing method of the present invention;
FIG. 2 is a block diagram of an httpClient-based access request processing system according to 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.
Referring to fig. 1, an embodiment of the present invention discloses an httpparent-based access request processing method, including the following steps:
step 1, setting corresponding httpClient for each preset timeout in advance;
step 2, carrying out overtime time configuration of different dimensions in advance by using hospital id and uri interfaces according to service requirements;
step 3, receiving an interface request for accessing the hospital ERP system, analyzing a hospital id interface and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
step 4, determining the overtime of the request interface according to the overtime configuration corresponding to the interface request;
step 5, loading the corresponding httpClient to call the interface according to the overtime of the request interface;
and 6, fusing the interface by httpClient according to the built-in timeout.
Correspondingly, referring to fig. 2, the present invention further provides an httpparent access request processing system, including:
the initialization module is used for presetting corresponding httpClient for each preset timeout;
the overtime configuration module is used for carrying out overtime configuration with different dimensions in advance through hospital id and uri interfaces according to business requirements;
the http-center module is used for receiving an interface request for accessing the hospital ERP system, analyzing a hospital id and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
the overtime time determining module is used for determining the overtime time of the request interface according to the overtime time configuration corresponding to the interface request;
the httpClient calling module is used for loading the corresponding httpClient to carry out interface calling according to the overtime of the request interface;
and the httpClient fusing module is used for fusing the interface according to the built-in timeout time of the httpClient.
In this embodiment, the access request processing method of httpparent takes the access request processing system of httpparent as an execution object of a step, or takes a component in the access request processing system of httpparent as an execution object of a step. Specifically, step 1 takes an initialization module as an execution object of the step, step 2 takes a timeout period configuration module as an execution object of the step, step 3 takes an http-center module as an execution object of the step, step 4 takes a timeout period determination module as an execution object of the step, step 5 takes an httpparent calling module as an execution object of the step, and step 6 takes an httpparent fusing module as an execution object of the step.
In the step 1, setting corresponding httpparent for each preset timeout so as to call the corresponding httpparent to fuse the interface in the step 5; for example, if the preset timeout periods are 5s, 8s, 10s, 15s, 20s, 30s, and 60s, respectively, an httpparent is preset for 5s, 8s, 10s, 15s, 20s, 30s, and 60s, respectively.
And step 2, setting corresponding timeout time configuration for the corresponding interface according to requirements.
Because the system performance and the network condition of each hospital are different, and a large difference exists between the access request numbers, the normal access request time of each hospital is also different, so different timeout time configurations need to be set for different hospitals, namely, one timeout time configuration is set for the hospital total interface according to the id of different hospitals.
Because each hospital also includes various interfaces, such as a registration interface, an appointment interface, an inquiry interface and the like, corresponding overtime configuration is required to be independently carried out on some interfaces with frequent access requests; for example, the registration and reservation interfaces are common request interfaces, and the number of requests is large, so that corresponding timeout time configuration needs to be performed on such interfaces, and the fusing of the timeout time is performed according to the normal request time of the interfaces; and for other interfaces which are not commonly used, such as report inquiry and the like, overtime time configuration is uniformly carried out according to the normal request time under the hospital, namely interface fusing is carried out according to the normal request time under the hospital interface.
For example, under a certain hospital main interface, there are a registration interface, an appointment interface, a payment interface, a report inquiry interface, etc., and an overtime time configuration is set for the hospital main interface according to the normal request time of the hospital main interface; because the registration interface, the reservation interface and the payment interface are interfaces with frequent access requests, overtime time configuration is set for the registration interface, the reservation interface and the payment interface respectively; the report query interface is an infrequent interface, that is, an interface with infrequent requests, so that timeout time configuration does not need to be set for the report query interface alone, and the timeout time configuration of the report query interface is timeout time configuration under a hospital total interface. When the http-center module receives the access request, if the accessed interface is a report query interface, the overtime configuration of the total interface of the hospital is taken as the standard; if the accessed interface is a registration interface, an appointment interface or a payment interface, the overtime time configuration independently set by the corresponding interface is taken as the standard, but the overtime time configuration of the total interface of the hospital is not taken as the standard; and after the corresponding overtime configuration is obtained respectively, fusing the interface by the corresponding overtime.
Specifically, in step 2, the step of performing timeout time configuration with different dimensions in advance through hospital id and uri interfaces according to the service requirements specifically includes:
and carrying out overtime configuration on each hospital total interface by using each hospital id, and then carrying out overtime configuration on each uri interface under each hospital according to business needs, wherein the priority level of the overtime configuration of each uri interface is greater than that of the hospital total interface.
Correspondingly, the overtime configuration module is specifically configured to perform overtime configuration on each hospital total interface by using each hospital id, and then perform overtime configuration on each uri interface under each hospital according to service needs, wherein the priority level of the overtime configuration of each uri interface is greater than the overtime configuration of the hospital total interface.
In the embodiment of the invention, when overtime time configuration is carried out, overtime time configuration is carried out on each uri interface under each hospital according to business needs, and priority sequencing is carried out on the uri interfaces and the hospital total interfaces, so that each uri interface can be fused within the accurate overtime time. For example, when the interface requests access to a registration interface, the registration interface has two timeout period configurations, one timeout period configuration is set for the registration interface alone, and the other timeout period configuration is the hospital master interface corresponding to the registration interface.
In step 3, since the timeout time configurations of each interface are different, the hospital id and the uri interfaces in the request need to be analyzed according to the interface request for accessing the hospital ERP system, that is, which interface under which hospital the access request requires to access is determined, so that the timeout time configuration corresponding to the access interface request is determined according to the preset in step 2.
As shown in the above example, if the interface requests access to the report query interface under the hospital, the timeout configuration of the total interface of the hospital is used as the timeout configuration of the interface request; and if the interface requests to access the registration interface under the hospital, the overtime configuration of the registration interface is used as the overtime configuration of the interface request, and the overtime configuration of the total interface of the hospital is not used as the overtime configuration of the interface request.
In step 4, after determining the timeout period configuration corresponding to the access interface request in step 3, determining the timeout period of the access interface request according to the timeout period configuration; specifically, the timeout time of the request interface is determined by the following substeps:
step 401, acquiring corresponding request time historical data within a preset time according to the timeout time configuration corresponding to the interface request;
step 402, determining an average value of the request time historical data according to the request time historical data, wherein the average value is used as the timeout time of the request interface.
Correspondingly, the timeout time determining module in the httpparent-based access request processing system comprises:
the historical data acquisition unit is used for acquiring corresponding request time historical data within preset time according to the overtime configuration corresponding to the interface request;
and the overtime calculation unit is used for determining the average value of the request time historical data according to the request time historical data, and the average value is used as the overtime of the request interface.
Accordingly, step 4 takes the timeout period determination module as the execution object of the step, or takes the component in the timeout period determination module as the execution object of the step, specifically, step 401 takes the history data acquisition unit as the execution object of the step, and step 402 takes the timeout period calculation unit as the execution object of the step.
In the embodiment of the invention, after the overtime configuration corresponding to the corresponding interface request is determined, the request time historical data of the corresponding interface is obtained, so that the average value of the request time historical data is obtained and is used as the overtime of the request interface, and the interface is fused by the overtime.
In the embodiment of the invention, the average value of the historical data of the request time is used as the reference of the normal request time of the request interface, so that the accurate overtime time can be set for each request of the corresponding interface, and when the average value is exceeded, the access request is fused, thereby effectively ensuring the normal operation of the server and avoiding service avalanche.
Specifically, in step 401, when the timeout time corresponding to the interface request is configured as the timeout time configuration of the total interfaces of the hospital, the request time history data is the request time history data of all interfaces of the hospital.
Correspondingly, in the historical data obtaining unit, when the timeout time corresponding to the interface request is configured as the timeout time configuration of the hospital total interface, the request time historical data is the request time historical data of all interfaces of the hospital.
In the embodiment of the invention, when the overtime configuration of the interface which the interface requests to access is the overtime configuration of the total interface of the hospital, the acquired time history data is the request time history data of all the interfaces of the hospital, and the request time history data of all the interfaces under the total interface of the hospital is used for averaging. For example, when the interface requests access to the report query interface, the historical data of the request time of all interfaces under the hospital is obtained to be averaged, and then the averaged value is used as the timeout time of the report query interface.
Of course, the overtime configuration of the hospital master interface may also be set to be a fixed time overtime, which is not limited by the present invention. For example, the timeout time of the total interface of the hospital is set to 30s, and when the interface requests to access the report query interface, the timeout time corresponding to the request interface is 30 s; and when the interface access is the interface which is independently set with the overtime configuration, such as a registration interface, a payment interface and the like, the overtime is determined according to the overtime configuration of the interface.
Specifically, in step 401, when the timeout time corresponding to the interface request is configured as a uri interface, the request time history data is the request time history data corresponding to the uri interface.
Correspondingly, in the history data obtaining unit, when the timeout time corresponding to the interface request is configured as the uri interface, the request time history data is the request time history data corresponding to the uri interface.
In the embodiment of the invention, when the interface which the interface requests to access is the uri interface which is configured with the independent overtime, and if the interface which the interface requests to access is the registration interface, the payment interface and other interfaces which are configured with the independent overtime, the request time historical data is the request time historical data under the corresponding interface. For example, if the interface which the interface requests to access is a registered interface, the request time history data is the request time history data under the registered interface; if the interface which the interface requests to access is a payment interface, the request time historical data is the request time historical data under the payment interface, and so on; therefore, the accurate overtime time can be determined for the interface used at high frequency more accurately, so that the system thread resource is protected, and the smooth operation of the server is ensured.
In step 5, after the timeout time corresponding to the request interface is determined, the httpparent preset and corresponding in step 1 is loaded to perform interface call, and the httpparent performs interface fusing according to the built-in timeout time in step 1. For example, if the timeout time corresponding to the request interface is 5s, invoking httpparent corresponding to 5s, and fusing the interface request when the httpparent module determines that the request interface time exceeds 5s, so as to avoid occupying thread resources; if the timeout time corresponding to the request interface is 10s, calling httpClient corresponding to 10s, and fusing the interface request when the httpClient module judges that the time of the request interface exceeds 10s so as to avoid occupying thread resources. When the httpClient module fuses the interface request, the user needs to send the request again to access the corresponding interface.
In summary, according to the invention, timeout time configurations of different dimensions are performed according to hospital id and uri interfaces, when an interface request for accessing the hospital ERP system is received, the hospital id and uri interfaces in the request are analyzed according to the interface request to determine the timeout time configuration corresponding to the interface request, so as to determine the timeout time corresponding to each interface, and finally, the httpparent is blown according to the timeout time request, so that when the hospital ERP system is unstable in service, the timeout fusing can be performed according to the timeout times of different interfaces, the thread resources of the system are protected, and the propagation of service failure is prevented.
The invention sets different overtime time configurations for different hospitals and different service interfaces according to service requirements to carry out interface fusing, thereby solving the problem that accurate overtime time cannot be set to cause service avalanche due to different system performances and network conditions of each hospital.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. An httpClient-based access request processing method is characterized by comprising the following steps:
step 1, setting corresponding httpClient for each preset timeout in advance;
step 2, carrying out overtime time configuration of different dimensions in advance by using hospital id and uri interfaces according to service requirements;
step 3, receiving an interface request for accessing the hospital ERP system, analyzing a hospital id interface and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
step 4, determining the overtime of the request interface according to the overtime configuration corresponding to the interface request;
step 5, loading the corresponding httpClient to call the interface according to the overtime of the request interface;
and 6, fusing the interface by httpClient according to the built-in timeout.
2. The httpparent-based access request processing method according to claim 1, wherein step 4 comprises:
step 401, acquiring corresponding request time historical data within a preset time according to the timeout time configuration corresponding to the interface request;
step 402, determining an average value of the request time historical data according to the request time historical data, wherein the average value is used as the timeout time of the request interface.
3. The httpparent-based access request processing method according to claim 2, wherein in step 401, when the timeout period corresponding to the interface request is configured as the timeout period of the hospital total interface, the request time history data is the request time history data of all interfaces of the hospital.
4. The httpparent-based access request processing method according to claim 2, wherein in step 401, when the timeout time corresponding to the interface request is configured as the uri interface, the request time history data is the request time history data corresponding to the uri interface.
5. The httpparent-based access request processing method according to claim 1, wherein in step 1, the step of performing timeout time configuration of different dimensions in advance according to service requirements by using hospital id and uri interfaces comprises:
and carrying out overtime configuration on each hospital total interface by using each hospital id, and then carrying out overtime configuration on each uri interface under each hospital according to business needs, wherein the priority level of the overtime configuration of each uri interface is greater than that of the hospital total interface.
6. An httpClient-based access request processing system is characterized by comprising
The initialization module is used for presetting corresponding httpClient for each preset timeout;
the overtime configuration module is used for carrying out overtime configuration with different dimensions in advance through hospital id and uri interfaces according to business requirements;
the http-center module is used for receiving an interface request for accessing the hospital ERP system, analyzing a hospital id and a uri interface in the request according to the interface request, and then determining timeout time configuration corresponding to the interface request according to an analysis result;
the overtime time determining module is used for determining the overtime time of the request interface according to the overtime time configuration corresponding to the interface request;
the httpClient calling module is used for loading the corresponding httpClient to carry out interface calling according to the overtime of the request interface;
and the httpClient fusing module is used for fusing the interface according to the built-in timeout time of the httpClient.
7. The httpparent-based access request processing system of claim 6, wherein the timeout period determination module comprises:
the historical data acquisition unit is used for acquiring corresponding request time historical data within preset time according to the overtime configuration corresponding to the interface request;
and the overtime calculation unit is used for determining the average value of the request time historical data according to the request time historical data, and the average value is used as the overtime of the request interface.
8. The httpparent-based access request processing system according to claim 7, wherein in the history data obtaining unit, when the timeout time corresponding to the interface request is configured as the timeout time of the hospital total interface, the request time history data is the request time history data of all interfaces of the hospital.
9. The httpparent-based access request processing system according to claim 7, wherein in the history data obtaining unit, when the timeout period corresponding to the interface request is configured as a uri interface, the request time history data is the request time history data corresponding to the uri interface.
10. The httpparent-based access request processing system according to claim 6, wherein the timeout period configuration module is specifically configured to configure the timeout period for each hospital total interface by each hospital id, and then configure the timeout period for each uri interface under each hospital according to business needs, wherein the priority level of the timeout period configuration for each uri interface is greater than the timeout period configuration for the hospital total interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110396882.8A CN113114505B (en) | 2021-04-13 | 2021-04-13 | httpClient-based access request processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110396882.8A CN113114505B (en) | 2021-04-13 | 2021-04-13 | httpClient-based access request processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113114505A CN113114505A (en) | 2021-07-13 |
| CN113114505B true CN113114505B (en) | 2022-07-12 |
Family
ID=76716450
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110396882.8A Active CN113114505B (en) | 2021-04-13 | 2021-04-13 | httpClient-based access request processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113114505B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090610A (en) * | 2021-11-11 | 2022-02-25 | 上海哔哩哔哩科技有限公司 | Database access method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108683604A (en) * | 2018-04-03 | 2018-10-19 | 平安科技（深圳）有限公司 | concurrent access control method, terminal device and medium |
| CN110138837A (en) * | 2019-04-15 | 2019-08-16 | 平安科技（深圳）有限公司 | Request processing method, device, computer equipment and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9665391B2 (en) * | 2012-05-17 | 2017-05-30 | International Business Machines Corporation | Automated transaction tuning in application servers |
| CN105721519B (en) * | 2014-12-02 | 2019-02-05 | 阿里巴巴集团控股有限公司 | A kind of webpage data acquiring method, apparatus and system |
| CN107196800B (en) * | 2017-05-27 | 2021-03-16 | 浪潮通用软件有限公司 | Overtime hierarchical control method based on configuration |
| CN111600738B (en) * | 2020-03-30 | 2022-12-09 | 福建天泉教育科技有限公司 | Method for optimizing timeout processing and storage medium |
| CN111858086B (en) * | 2020-06-15 | 2023-07-21 | 福建天泉教育科技有限公司 | Processing method and storage medium for queue timeout in request task processing |
-
2021
- 2021-04-13 CN CN202110396882.8A patent/CN113114505B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108683604A (en) * | 2018-04-03 | 2018-10-19 | 平安科技（深圳）有限公司 | concurrent access control method, terminal device and medium |
| CN110138837A (en) * | 2019-04-15 | 2019-08-16 | 平安科技（深圳）有限公司 | Request processing method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113114505A (en) | 2021-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110858843B (en) | Service request processing method and device and computer readable storage medium | |
| CN108776934B (en) | Distributed data calculation method and device, computer equipment and readable storage medium | |
| EP2807553B1 (en) | Managing data transfers over network connections based on priority and a data usage plan | |
| CN111010426A (en) | Message pushing method and device | |
| US9323588B2 (en) | Service platform architecture | |
| CN107819797B (en) | Access request processing method and device | |
| CN107222646B (en) | Call request distribution method and device | |
| CN110308985B (en) | Cloud exclusive server resource management method, device, equipment and storage medium | |
| CN112953840A (en) | Current limiting control method, gateway equipment and current limiting control system | |
| CN107995286B (en) | Automatic service starting and stopping method based on dubbo platform, server and storage medium | |
| WO2019237591A1 (en) | File format conversion method and apparatus, computer device, and storage medium | |
| JP3487425B2 (en) | Congestion control method and method | |
| CN114500288B (en) | Bandwidth adjustment method and device and storage medium | |
| CN107786998A (en) | A kind of processing method of network connection, device, equipment and computer-readable storage medium | |
| CN109617750A (en) | A service early warning method and gateway | |
| CN113114505B (en) | httpClient-based access request processing method and system | |
| US20070240169A1 (en) | Computer implemented method for removing an event registration within an event notification infrastructure | |
| CN115103007A (en) | Distributed cloud-based service discovery method, device and readable storage medium | |
| CN110019372A (en) | Data monitoring method, device, server and storage medium | |
| CN109905407B (en) | Management method, system, device and medium for accessing intranet based on VPN server | |
| CN110471966B (en) | Information data verification method, device, computer equipment and storage medium | |
| CN109743416B (en) | CDN domain name scheduling method, device, computer readable storage medium and system | |
| CN112087336A (en) | Deployment and management method and device of virtual IP service system and electronic equipment | |
| CN115037693B (en) | Distributed current limiting method and distributed current limiting device based on token bucket | |
| CN111488373A (en) | Method and system for processing request |
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 |