CN109842672B

CN109842672B - Service request distribution method and device, computer equipment and storage medium

Info

Publication number: CN109842672B
Application number: CN201811527511.3A
Authority: CN
Inventors: 苏渊博
Original assignee: Ping An Puhui Enterprise Management Co Ltd
Current assignee: Ping An Puhui Enterprise Management Co Ltd
Priority date: 2018-12-13
Filing date: 2018-12-13
Publication date: 2022-11-11
Anticipated expiration: 2038-12-13
Also published as: CN109842672A

Abstract

The invention discloses a service request distribution method, a service request distribution device, computer equipment and a storage medium. The method comprises the following steps: if the access request and the request address corresponding to the access request are detected, receiving and analyzing the request address; according to the analysis information of the request address, acquiring a system with a version corresponding to the analysis information and a resource of the system; and if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource. The method realizes that developers directly access the service system according to the request address and acquire the system with the corresponding version and the resources of the system to directly carry out logic development of the system, thereby avoiding local configuration and improving the development efficiency.

Description

Service request distribution method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of internet technologies, and in particular, to a service request distribution method and apparatus, a computer device, and a storage medium.

Background

Currently, when an extranet person or an intranet developer accesses a service system and acquires an interface of the service system, the extranet person or the intranet developer needs to communicate with an operation maintenance person of the service system about the relevant matters in the interface, so that the efficiency of accessing or maintaining the service system is low. When an intranet developer accesses the service system for development, the intranet developer needs to configure locally according to the service system, and development efficiency is low.

Disclosure of Invention

The embodiment of the invention provides a service request distribution method, a service request distribution device, computer equipment and a storage medium, and aims to solve the problem that in the prior art, when an intranet developer accesses a service system for development, the intranet developer needs to configure locally according to the system, so that the development efficiency is low.

In a first aspect, an embodiment of the present invention provides a service request distribution method, which includes:

if the access request and the request address corresponding to the access request are detected, receiving and analyzing the request address;

according to the analysis information of the request address, acquiring a system with a version corresponding to the analysis information and a resource of the system;

and if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource.

In a second aspect, an embodiment of the present invention provides a service request distribution apparatus, including:

the access request analysis unit is used for receiving and analyzing the request address if the access request and the request address corresponding to the access request are detected;

the resource acquisition unit is used for acquiring a system with a version corresponding to the analysis information and a resource of the system according to the analysis information of the request address;

and the resource editing unit is used for acquiring the editing content corresponding to the editing instruction if the editing instruction of the system resource is detected, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource.

In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the processor implements the service request distribution method according to the first aspect.

In a fourth aspect, the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, causes the processor to execute the service request distribution method according to the first aspect.

The embodiment of the invention provides a service request distribution method, a service request distribution device, computer equipment and a storage medium. If an access request and a request address corresponding to the access request are detected, receiving and analyzing the request address; according to the analysis information of the request address, acquiring a system with a version corresponding to the analysis information and a resource of the system; and if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource. The method realizes that developers directly access the service system according to the request address and acquire the system with the corresponding version and the resources of the system to directly carry out logic development of the system, thereby avoiding local configuration and improving the development efficiency.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flow chart of a service request distribution method according to an embodiment of the present invention;

fig. 2 is a sub-flow diagram of a service request distribution method according to an embodiment of the present invention;

fig. 3 is another sub-flow diagram of the service request distribution method according to the embodiment of the present invention;

fig. 4 is another sub-flow diagram of a service request distribution method according to an embodiment of the present invention;

fig. 5 is a schematic block diagram of a service request distribution apparatus provided by an embodiment of the present invention;

FIG. 6 is a schematic block diagram of sub-units of a service request distribution apparatus provided by an embodiment of the present invention;

FIG. 7 is a schematic block diagram of another sub-unit of a service request distribution apparatus provided by an embodiment of the present invention;

FIG. 8 is a schematic block diagram of another sub-unit of a service request distribution apparatus provided by an embodiment of the present invention;

FIG. 9 is a schematic block diagram of a computer device provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. 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.

It will 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 invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting. 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 this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

Referring to fig. 1, fig. 1 is a schematic flowchart of a service request distribution method according to an embodiment of the present invention, where the service request distribution method is applied to an intelligent terminal, and the method is executed by application software installed in the intelligent terminal.

As shown in fig. 1, the method includes steps S110 to S130.

And S110, receiving and analyzing the request address if the access request and the request address corresponding to the access request are detected.

In this embodiment, when a user (mainly, a developer) needs to access a resource of a certain system in a certain domain name under a certain version and obtain an operation meeting an operation condition for the resource, a request address needs to be edited, the resource is located by a server through the request address, and a corresponding operation is performed on the resource; for example, in the present application, the format of the customized request address is as follows:

request address format of the internal lan: domain name/system/version/resource/operator

Condition 1= x&Condition 2=y.;

request address format of the external network: domain name/aaa/system/version/resource/operator

Condition 1= x&Condition 2= y.;

when the server receives the access request and the request address corresponding to the access request, the request address needs to be analyzed. As can be seen from the two common request address formats, in order to obtain the meaning of each segment of the request address, the number of the separation identifiers "/" in the request address needs to be counted first, and the request address is divided into multiple segments by the separation identifiers "/", where each segment represents the different meaning. For example, request address format on the extranet (domain name/aaa/system/version/resource/operator)

Condition 1= x&In condition 2= y. -), 5 partition identifiers "/" are included, and the 5 partition identifiers divide the request address into 6 segments, each segment corresponding to one piece of segment information. After the request address is obtained, received and analyzed, the system and the resource which the user needs to access can be accurately positioned.

In one embodiment, as shown in fig. 2, step S110 includes:

s111, receiving a request address, and counting the number of the separation identifiers in the request address;

s112, if the number of the separation identifiers in the request address is 5, sequentially acquiring 6 pieces of segmentation information, and respectively recording the segmentation information as first segmentation information to sixth segmentation information;

s113, judging whether the first section information is a domain name, if the first section information is the domain name, executing a step of judging whether the second section information is a company name identification character string, and if the first section information is not the domain name, prompting a re-editing request address;

s114, judging whether the second section information is a company name identification character string, if the second section information is the company name identification character string, executing a step of judging whether the third section information is a system name character string, and if the second section information is not the company name identification character string, prompting a re-editing request address;

s115, judging whether the third section information is a system name character string, if the third section information is the system name character string, executing a step of judging whether the fourth section information is a system version number character string, and if the third section information is not the system name character string, prompting a re-editing request address;

s116, judging whether the fourth segment information is a system version number character string, if the fourth segment information is the system version number character string, executing the step of judging whether the fifth segment information is a resource identifier of the system, and if the fourth segment information is not the system version number character string, prompting a re-editing request address;

s117, judging whether the fifth section information is a resource identifier of the system, if the fifth section information is the resource identifier of the system, executing the step of judging whether the sixth section information is an operator, and if the fifth section information is not the resource identifier of the system, prompting a re-editing request address;

and S118, judging whether the sixth segment information is an operator, if the sixth segment information is the operator, prompting to complete the analysis of the request address, and if the sixth segment information is not the operator, prompting to re-edit the request address.

In this embodiment, the prompt re-edit request address can be regarded as step S1181. When it is known that the number of the separation identifiers in the request address is 5, the request is denoted as an extranet request, and at this time, the following operations are sequentially performed:

determining whether the first segment information is a domain name, for example, determining whether the first segment information satisfies a domain name format such as "www.xxx.com.cn"; if the domain name format of 'www.xxx.com.cn' is satisfied, judging the second segment, and if the domain name format of 'www.xxx.com.cn' is not satisfied, prompting the user to re-edit the request address;

determining whether the second piece of segment information is a company name identification string (e.g., the company name identification string of aaa company is aaa), for example, determining whether the second piece of segment information satisfies a company name identification string format such as "aaa"; if the company name identification character string format of 'aaa' is satisfied, judging the third section, and if the company name identification character string format of 'aaa' is not satisfied, prompting the user to re-edit the request address;

judging whether the third segment of information is a system name character string (for example, the system name character string of a 020 system is 020) or not, for example, judging whether the third segment of information meets a system name character string format such as "020"; if the system name character string format of '020' is met, judging the fourth segment, and if the system name character string format of '020' is not met, prompting a user to re-edit the request address;

judging whether the fourth segment information is a system version number character string (for example, the system version number character string of the V1 version is V1), for example, judging whether the fourth segment information meets the system version number character string format like V1; if the character string format of the system version number like V1 is met, judging the fifth section, and if the character string format of the system version number like V1 is not met, prompting a user to re-edit the request address;

judging whether the fifth segment information is a resource identifier (for example, the resource identifier of a user resource is a user), for example, judging whether the fifth segment information meets a resource identifier format such as "user"; if the resource identifier format of the user is satisfied, judging the sixth segment, and if the resource identifier format of the user is not satisfied, prompting the user to re-edit the request address;

judging whether the sixth segmentation information is an operator (for example, the operator of the cert operation is cert), for example, judging whether the sixth segmentation information meets the operator format such as "cert"; if the operator format such as 'cert' is satisfied, the analysis of the request address is prompted to be completed, and if the operator format such as 'cert' is not satisfied, the prompt of re-editing the request address is given to the user.

Therefore, in the embodiment, the interface can be accessed according to the analysis information by inputting the request address by the user, and clear transactions in the interface do not need to be communicated, so that the development efficiency is improved.

In one embodiment, the step S111 includes:

acquiring the IP address of a sender of the request address, and judging whether the IP address of the sender is the same as a preset intranet address or not;

if the IP address of the sender is the same as the preset intranet address, setting the number of the separation identifiers in the request address to be 4;

and if the IP address of the sender is different from the preset intranet address, setting the number of the separation identifiers in the request address to be 5.

In this embodiment, if the IP address of the sender is the same as the preset intranet address, and it is determined that the sender of the request address belongs to a user in the same intranet, it may be determined that the number of the separation identifiers in the request address is 4; if the IP address of the sender is different from the preset intranet address, the sender of the request address is determined not to belong to the user of the same intranet, and then the number of the separation identifiers in the request address can be determined to be 5.

The number of the separation identifiers in the request uploaded by the user can be quickly judged by judging whether the IP address of the sender is the same as the preset intranet address, because the user needs to edit the position of the resource of the system according to the preset format of the request address in order to correctly position the resource of the system, the number of the separation identifiers in the request address can be quickly counted by judging whether the IP address of the sender is the same as the preset intranet address.

In one embodiment, as shown in fig. 3, step S110 includes:

s1191, if the number of the separation identifiers in the request address is 4, sequentially acquiring 5 pieces of segmentation information, and respectively recording as eleventh segmentation information to fifteenth segmentation information;

s1192, determine whether the eleventh segment information is a domain name, if the eleventh segment information is the domain name, execute the step of determining whether the twelfth segment information is a system name string, if the eleventh segment information is not the domain name prompt re-edit request address;

s1193, judge whether the twelfth segmentation information is a system name string, if the twelfth segmentation information is a system name string, execute the step of judging whether the thirteenth segmentation information is a system version number character, if the twelfth segmentation information is not a system name string prompt re-edit request address;

s1194, judge whether the thirteenth sectional information is a system version number character string, if the thirteenth sectional information is a system version number character string, execute the step of judging whether the fourteenth sectional information is a resource identifier of the system, if the thirteenth sectional information does not prompt the re-editing request address for the system version number character string;

s1195, determine whether the fourteenth segment information is the resource identifier of the system, if the fourteenth segment information is the resource identifier of the system, execute the step of determining whether the fifteenth segment information is an operator, if the fourteenth segment information is not the resource identifier of the system, prompt to re-edit the request address;

s1196, determine whether the fifteenth segment information is an operational character, if the fifteenth segment information is the operational character, obtain the resolution information of the request address, and if the fifteenth segment information does not prompt the operational character to re-edit the request address.

In this embodiment, when the number of the separation identifiers in the request address is 4, the difference from the request address where the number of the separation identifiers is 5 is that the second piece of segment information is no longer the company name identification character string, but is the system name character string, that is, one piece of segment information in the request address sent by the intranet user, which is less than the request address sent by the extranet user, is the company name identification character string. As another embodiment of resolving the request address, it also simplifies the process of knowing the interface information in the user access process.

And S120, acquiring a system with a version corresponding to the analysis information and system resources according to the analysis information of the request address.

In one embodiment, as shown in fig. 4, step S120 includes:

s121, establishing an initial system environment according to the analysis information of the request address;

s122, configuring the initial system environment according to the system of the version corresponding to the analysis information to obtain the current system environment;

s123, acquiring the system resource corresponding to the analysis information, and deploying the logic code included in the system resource in the current system environment.

In this embodiment, after the server parses the request address information sent by the user and obtains the parsed information of the request address correspondingly, the system of the corresponding version and the resource of the system may be located at the server, the resource of the system may be understood as the logic code file included in the system, and the user may modify and edit the logic code file after entering the system, so as to complete the development work. Namely, developers do not need to pay attention to the system, and only need to pay attention to the logic development of the system in charge, so that local configuration (the system in charge is pre-configured) is avoided, namely, the developers directly input request addresses each time the developers enter the system.

S130, if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource.

In this embodiment, when the server receives the editing content of the user, the resources of the system may be adjusted according to the editing content, so as to complete logic development. Therefore, the system in charge of the technical developers can be quickly positioned, the resources of the system can be edited and modified on line without downloading to the local, and the time spent on knowing the interface details and the configuration information in the development process is avoided.

In an embodiment, step S130 is followed by:

and acquiring the editing content, and correspondingly storing the editing content as a modification log.

In this embodiment, in order to clearly know the modification made by the developer to the system resource each time, the edited content of this time may be obtained and stored as a modification log, so that the subsequent developer can refer to the historical modification information conveniently.

The method realizes that developers directly access the service system according to the request address and acquire the system with the corresponding version and the resources of the system to directly carry out logic development of the system, thereby avoiding local configuration and improving the development efficiency.

The embodiment of the invention also provides a service request distribution device, which is used for executing any embodiment of the service request distribution method. Specifically, please refer to fig. 5, wherein fig. 5 is a schematic block diagram of a service request distribution apparatus according to an embodiment of the present invention. The service request distribution apparatus 100 may be configured in an intelligent terminal.

As shown in fig. 5, the service request distribution apparatus 100 includes an access request parsing unit 110, a resource obtaining unit 120, and a resource editing unit 130.

The access request parsing unit 110 is configured to receive and parse the request address if the access request and the request address corresponding to the access request are detected.

In this embodiment, when a user (mainly, a developer) needs to access a resource of a certain system in a certain domain name in a certain version and obtain an operation meeting an operation condition for the resource, a request address needs to be edited, the resource is located by a server through the request address, and a corresponding operation is performed on the resource; for example, in the present application, the format of the customized request address is as follows:

request address format of the internal lan: domain name/system/version/resource/operationSymbol

Condition 1= x&Condition 2=y.;

Condition 1= x&Condition 2= y.;

In an embodiment, as shown in fig. 6, the access request parsing unit 110 includes:

a counting unit 111, configured to receive a request address, and count the number of the separation identifiers in the request address;

a first sequence number allocation unit 112, configured to obtain 6 pieces of segment information in sequence if the number of the separation identifiers in the request address is 5, and record the 6 pieces of segment information as first segment information to sixth segment information respectively;

a first segmentation judging unit 113, configured to judge whether the first segmentation information is a domain name, perform a step of judging whether the second segmentation information is a company name identification string if the first segmentation information is the domain name, and prompt a re-editing request address if the first segmentation information is not the domain name;

a second segment determining unit 114, configured to determine whether the second segment information is a company name identification character string, execute a step of determining whether the third segment information is a system name character string if the second segment information is the company name identification character string, and prompt a re-edit request address if the second segment information is not the company name identification character string;

a third segment determining unit 115, configured to determine whether the third segment information is a system name string, execute a step of determining whether the fourth segment information is a system version number string if the third segment information is the system name string, and prompt a re-edit request address if the third segment information is not the system name string;

a fourth segmentation judging unit 116, configured to judge whether the fourth segmentation information is a system version number character string, if the fourth segmentation information is a system version number character string, execute a step of judging whether the fifth segmentation information is a resource identifier of the system, and if the fourth segmentation information is not the system version number character string, prompt to re-edit the request address;

a fifth segmentation judging unit 117, configured to judge whether the fifth segmentation information is a resource identifier of the system, execute a step of judging whether the sixth segmentation information is an operator if the fifth segmentation information is the resource identifier of the system, and prompt a re-edit request address if the fifth segmentation information is not the resource identifier of the system;

a sixth segmentation judging unit 118, configured to judge whether the sixth segmentation information is an operator, if the sixth segmentation information is an operator, the request address is analyzed, and if the sixth segmentation information is not an operator, the request address is re-edited.

In the present embodiment, the prompt re-edit request address can be regarded as the address re-edit prompt unit 1181. When it is known that the number of the separation identifiers in the request address is 5, the request is denoted as an extranet request, and at this time, the following operations are sequentially performed:

determining whether the first segment information is a domain name, for example, determining whether the first segment information satisfies a domain name format such as "www.xxx.com.cn"; if the domain name format of 'www.xxx.com.cn' is met, judging the second segment, and if the domain name format of 'www.xxx.com.cn' is not met, prompting a user to re-edit the request address;

judging whether the third segment information is a system name character string (for example, the system name character string of a 020 system is 020) or not, for example, judging whether the third segment information meets a system name character string format such as "020" or not; if the system name character string format of '020' is met, judging the fourth segment, and if the system name character string format of '020' is not met, prompting a user to re-edit the request address;

judging whether the fourth section information is a system version number character string (for example, the system version number character string of the V1 version is V1), for example, judging whether the fourth section information meets the system version number character string format such as V1; if the character string format of the system version number like V1 is met, judging the fifth section, and if the character string format of the system version number like V1 is not met, prompting a user to re-edit the request address;

judging whether the fifth segment information is a resource identifier (for example, the resource identifier of a user resource is a user), for example, judging whether the fifth segment information meets a resource identifier format such as "user"; if the resource identifier format of the user is met, judging the sixth segment, and if the resource identifier format of the user is not met, prompting a user to re-edit the request address;

judging whether the sixth segment information is an operator (for example, the operator of the cert operation is cert), for example, judging whether the sixth segment information meets the operator format such as "cert"; if the operator format such as 'cert' is satisfied, the analysis of the request address is prompted to be completed, and if the operator format such as 'cert' is not satisfied, the prompt of re-editing the request address is given to the user.

Therefore, in the embodiment, the interface can be accessed according to the analysis information by inputting the request address by the user, communication of clear transactions in the interface is not needed, and the development efficiency is improved.

In one embodiment, the statistic unit 111 includes:

the intranet IP judging unit is used for acquiring the sender IP address of the request address and judging whether the sender IP address is the same as a preset intranet address or not;

a first separator setting unit, configured to set the number of separator identifiers in the request address to 4 if the IP address of the sender is the same as a preset intranet address;

and the second separator setting unit is used for setting the number of the separator identifiers in the request address to be 5 if the IP address of the sender is different from the preset intranet address.

The number of the separation identifiers in the request uploaded by the user can be quickly judged by judging whether the IP address of the sender is the same as the preset internal network address, and the user needs to edit according to the preset format of the request address in order to correctly position the position of the resource of the system, so that the number of the separation identifiers in the request address can be quickly counted by judging whether the IP address of the sender is the same as the preset internal network address.

In an embodiment, as shown in fig. 7, the access request parsing unit 110 includes:

a second sequence number allocation unit 1191, configured to obtain 5 pieces of segment information in sequence if the number of the separation identifiers in the request address is 4, and record the 5 pieces of segment information as eleventh segment information to fifteenth segment information respectively;

an eleventh segmentation judging unit 1192, configured to judge whether the eleventh segmentation information is a domain name, execute a step of judging whether the twelfth segmentation information is a system name string if the eleventh segmentation information is the domain name, and prompt a re-editing request address if the eleventh segmentation information is not the domain name;

a twelfth segmentation judging unit 1193, configured to judge whether the twelfth segmentation information is a system name string, execute a step of judging whether the thirteenth segmentation information is a system version number character if the twelfth segmentation information is the system name string, and prompt a re-editing request address if the twelfth segmentation information is not the system name string;

a thirteenth section judging unit 1194, configured to judge whether the thirteenth section information is a system version number string, execute the step of judging whether the fourteenth section information is a resource identifier of the system if the thirteenth section information is a system version number string, and prompt to re-edit the request address if the thirteenth section information is not the system version number string;

a fourteenth segmentation determining unit 1195 is configured to determine whether the fourteenth segmentation information is a resource identifier of the system, execute the step of determining whether the fifteenth segmentation information is an operator if the fourteenth segmentation information is the resource identifier of the system, and prompt a re-editing request address if the fourteenth segmentation information is not the resource identifier of the system;

a fifteenth segmentation determining unit 1196 is configured to determine whether the fifteenth segmentation information is an operator, obtain resolution information of the request address if the fifteenth segmentation information is the operator, and prompt the request address to be re-edited if the fifteenth segmentation information is not the operator.

The resource obtaining unit 120 is configured to obtain, according to the resolution information of the request address, a system and a resource of the system in a version corresponding to the resolution information.

In an embodiment, as shown in fig. 8, the resource obtaining unit 120 includes:

an initial system environment establishing unit 121, configured to correspondingly establish an initial system environment according to the analysis information of the request address;

a current system environment configuration unit 122, configured to configure the initial system environment according to the system of the version corresponding to the analysis information, so as to obtain a current system environment;

a code deploying unit 123, configured to acquire a resource of the system corresponding to the analysis information, and deploy a logic code included in the resource of the system in the current system environment.

In this embodiment, after the server parses the request address information sent by the user and obtains the parsed information of the request address correspondingly, the system of the corresponding version and the resource of the system may be located at the server, the resource of the system may be understood as the logic code file included in the system, and the user may modify and edit the logic code file after entering the system, so as to complete the development work. That is, the developer only needs to pay attention to the logic development of the system in charge without paying attention to the system, so that local configuration (the system in charge is pre-configured) is avoided, namely, the developer directly inputs a request address every time the developer enters the system.

And the resource editing unit 130 is configured to, if an editing instruction for the resource of the system is detected, acquire an editing content corresponding to the editing instruction, adjust the resource of the system according to the editing content, obtain an adjusted system resource, and store the adjusted system resource.

In an embodiment, the service request distribution apparatus 100 further includes:

and the modification log storage unit is used for acquiring the editing content and correspondingly storing the editing content as a modification log.

The device realizes that developers directly access the service system according to the request address and obtain the system with the corresponding version and the resources of the system to directly carry out logic development of the system, thereby avoiding local configuration and improving the development efficiency.

The service request distribution means described above may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 9.

Referring to fig. 9, fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present invention.

Referring to fig. 9, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.

The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032, when executed, may cause the processor 502 to perform a service request distribution method.

The processor 502 is used to provide computing and control capabilities that support the operation of the overall computer device 500.

The internal memory 504 provides an environment for running the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 may be caused to execute the service request distribution method.

The network interface 505 is used for network communication, such as providing transmission of data information. Those skilled in the art will appreciate that the configuration shown in fig. 9 is a block diagram of only a portion of the configuration associated with aspects of the present invention and is not intended to limit the computing device 500 to which aspects of the present invention may be applied, and that a particular computing device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

Wherein the processor 502 is configured to run the computer program 5032 stored in the memory to implement the following functions: if the access request and the request address corresponding to the access request are detected, receiving and analyzing the request address; according to the analysis information of the request address, acquiring a system with a version corresponding to the analysis information and a resource of the system; and if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource.

In one embodiment, the processor 502, when performing the step of receiving and resolving the request address, performs the following: receiving a request address, and counting the number of the separation identifiers in the request address;

if the number of the separation identifiers in the request address is 5, sequentially acquiring 6 pieces of segmentation information, and respectively recording the segmentation information as first segmentation information to sixth segmentation information;

judging whether the first section information is a domain name, if so, executing a step of judging whether the second section information is a company name identification character string, and if not, prompting a re-editing request address; judging whether the second section information is a company name identification character string, if the second section information is the company name identification character string, executing a step of judging whether the third section information is a system name character string, and if the second section information is not the company name identification character string, prompting a re-editing request address; judging whether the third section information is a system name character string, if so, executing a step of judging whether the fourth section information is a system version number character string, and if not, prompting a re-editing request address; judging whether the fourth segment information is a system version number character string, if the fourth segment information is the system version number character string, executing a step of judging whether the fifth segment information is a resource identifier of the system, and if the fourth segment information is not the system version number character string, prompting a re-editing request address; judging whether the fifth section information is a resource identifier of the system, if the fifth section information is the resource identifier of the system, executing a step of judging whether the sixth section information is an operator, and if the fifth section information is not the resource identifier of the system, prompting a re-editing request address; and judging whether the sixth segmentation information is an operator, if the sixth segmentation information is the operator, prompting to finish the analysis of the request address, and if the sixth segmentation information is not the operator, prompting to re-edit the request address.

In one embodiment, the processor 502, when performing the step of receiving and resolving the request address, performs the following: if the number of the separation identifiers in the request address is 4, sequentially acquiring 5 pieces of segmentation information, and respectively recording the segmentation information as eleventh segmentation information to fifteenth segmentation information; judging whether the eleventh segmentation information is a domain name, if so, executing a step of judging whether the twelfth segmentation information is a system name character string, and if not, prompting a re-editing request address for the domain name; judging whether the twelfth segmentation information is a system name character string, if so, executing a step of judging whether the thirteenth segmentation information is a system version number character, and if not, prompting a re-editing request address for the system name character string; judging whether the thirteenth segment information is a system version number character string, if the thirteenth segment information is the system version number character string, executing a step of judging whether the fourteenth segment information is a resource identifier of the system, and if the thirteenth segment information is not the system version number character string, prompting a re-editing request address; judging whether the fourteenth segmentation information is a resource identifier of the system, if so, executing a step of judging whether the fifteenth segmentation information is an operator, and if not, prompting a re-editing request address; and judging whether the fifteenth segmentation information is an operational character, if so, acquiring the resolution information of the request address, and if not, prompting to re-edit the request address.

In an embodiment, when the step of acquiring the system and the system resource corresponding to the resolution information according to the resolution information of the request address is executed, the processor 502 executes the following operations: establishing an initial system environment according to the analysis information of the request address; configuring the initial system environment according to the system of the version corresponding to the analysis information to obtain the current system environment; and acquiring resources of the system corresponding to the analysis information, and deploying the logic codes included in the resources of the system in the current system environment.

In an embodiment, after the step of acquiring the editing content corresponding to the editing instruction, adjusting the resource correspondence of the system according to the editing content, obtaining the adjusted system resource, and saving the adjusted system resource, the processor 502 further performs the following operations: and acquiring the editing content, and correspondingly storing the editing content as a modification log.

In an embodiment, when the step of receiving the request address and counting the number of the separation identifiers in the request address is performed, the processor 502 performs the following operations: acquiring the IP address of a sender of the request address, and judging whether the IP address of the sender is the same as a preset intranet address or not; if the IP address of the sender is the same as the preset intranet address, setting the number of the separation identifiers in the request address to be 4; and if the IP address of the sender is different from the preset intranet address, setting the number of the separation identifiers in the request address to be 5.

Those skilled in the art will appreciate that the embodiment of a computer device illustrated in fig. 9 does not constitute a limitation on the specific construction of the computer device, and that in other embodiments a computer device may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. For example, in some embodiments, the computer device may only include a memory and a processor, and in such embodiments, the structures and functions of the memory and the processor are consistent with those of the embodiment shown in fig. 9, and are not described herein again.

It should be understood that, in the embodiment of the present invention, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field-Programmable gate arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In another embodiment of the invention, a computer-readable storage medium is provided. The computer readable storage medium may be a non-volatile computer readable storage medium. The computer-readable storage medium stores a computer program, wherein the computer program when executed by a processor implements the steps of: if the access request and the request address corresponding to the access request are detected, receiving and analyzing the request address; acquiring a system of a version corresponding to the analysis information and a resource of the system according to the analysis information of the request address; and if the editing instruction of the system resource is detected, acquiring the editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource.

In one embodiment, the receiving and resolving the request address includes: receiving a request address, and counting the number of the separation identifiers in the request address; if the number of the separation identifiers in the request address is 5, sequentially acquiring 6 pieces of segmentation information, and respectively recording the segmentation information as first segmentation information to sixth segmentation information; judging whether the first section information is a domain name, if so, executing a step of judging whether the second section information is a company name identification character string, and if not, prompting a re-editing request address; judging whether the second section information is a company name identification character string, if the second section information is the company name identification character string, executing a step of judging whether the third section information is a system name character string, and if the second section information is not the company name identification character string, prompting a re-editing request address; judging whether the third section information is a system name character string, if so, executing a step of judging whether the fourth section information is a system version number character string, and if not, prompting a re-editing request address for the system name character string; judging whether the fourth segment information is a system version number character string, if the fourth segment information is the system version number character string, executing a step of judging whether the fifth segment information is a resource identifier of the system, and if the fourth segment information is not the system version number character string, prompting a re-editing request address; judging whether the fifth section information is a resource identifier of the system, if the fifth section information is the resource identifier of the system, executing a step of judging whether the sixth section information is an operator, and if the fifth section information is not the resource identifier of the system, prompting a re-editing request address; and judging whether the sixth segmentation information is an operator, if the sixth segmentation information is the operator, prompting to finish the analysis of the request address, and if the sixth segmentation information is not the operator, prompting to re-edit the request address.

In one embodiment, the receiving and resolving the request address includes: if the number of the separation identifiers in the request address is 4, sequentially acquiring 5 pieces of segment information, and respectively recording the 5 pieces of segment information as eleventh segment information to fifteenth segment information; judging whether the eleventh segmentation information is a domain name or not, if the eleventh segmentation information is the domain name, executing a step of judging whether the twelfth segmentation information is a system name character string or not, and if the eleventh segmentation information is not the domain name, prompting a re-editing request address; judging whether the twelfth segmentation information is a system name character string, if so, executing a step of judging whether the thirteenth segmentation information is a system version number character, and if not, prompting a re-editing request address; judging whether the thirteenth segment information is a system version number character string, if the thirteenth segment information is the system version number character string, executing a step of judging whether the fourteenth segment information is a resource identifier of the system, and if the thirteenth segment information is not the system version number character string, prompting a re-editing request address; judging whether the fourteenth segmentation information is a resource identifier of the system, if so, executing a step of judging whether the fifteenth segmentation information is an operator, and if not, prompting a re-editing request address; and judging whether the fifteenth segmentation information is an operational character, if so, acquiring the resolution information of the request address, and if not, prompting to re-edit the request address.

In an embodiment, the obtaining, according to the resolution information of the request address, the system and the system resource of the version corresponding to the resolution information includes: establishing an initial system environment according to the analysis information of the request address; configuring the initial system environment according to the system of the version corresponding to the analysis information to obtain the current system environment; and acquiring resources of the system corresponding to the analysis information, and deploying the logic codes included in the resources of the system in the current system environment.

In an embodiment, the obtaining of the editing content corresponding to the editing instruction, and adjusting the resource correspondence of the system according to the editing content to obtain and store the adjusted system resource further includes: and acquiring the editing content, and correspondingly storing the editing content as a modification log.

In an embodiment, the receiving a request address, and statistically acquiring the number of separation identifiers in the request address includes: acquiring the IP address of a sender of the request address, and judging whether the IP address of the sender is the same as a preset intranet address or not; if the IP address of the sender is the same as the preset intranet address, setting the number of the separation identifiers in the request address to be 4; and if the IP address of the sender is different from the preset intranet address, setting the number of the separation identifiers in the request address to be 5.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided by the present invention, it should be understood that the disclosed apparatus, device and method can be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only a logical division, and there may be other divisions when the actual implementation is performed, or units having the same function may be grouped into one unit, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electrical, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, and various media capable of storing program codes.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A service request distribution method, comprising:

if the editing instruction of the system resource is detected, acquiring editing content corresponding to the editing instruction, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource;

the acquiring a system of a version corresponding to the resolution information and a resource of the system according to the resolution information of the request address comprises: establishing an initial system environment according to the analysis information of the request address; configuring the initial system environment according to the system of the version corresponding to the analysis information to obtain the current system environment; and acquiring resources of the system corresponding to the analysis information, and deploying logic codes included in the resources of the system in the current system environment.

2. The method of claim 1, wherein the receiving and resolving the request address comprises:

receiving a request address, and counting the number of the separation identifiers in the request address;

judging whether the first section information is a domain name, if so, executing a step of judging whether the second section information is a company name identification character string, and if not, prompting a re-editing request address;

judging whether the second section information is a company name identification character string, if the second section information is the company name identification character string, executing a step of judging whether the third section information is a system name character string, and if the second section information is not the company name identification character string, prompting a re-editing request address;

judging whether the third section information is a system name character string, if so, executing a step of judging whether the fourth section information is a system version number character string, and if not, prompting a re-editing request address for the system name character string;

judging whether the fourth segment information is a system version number character string, if the fourth segment information is the system version number character string, executing a step of judging whether the fifth segment information is a resource identifier of the system, and if the fourth segment information is not the system version number character string, prompting a re-editing request address;

judging whether the fifth section information is a resource identifier of the system, if the fifth section information is the resource identifier of the system, executing a step of judging whether the sixth section information is an operator, and if the fifth section information is not the resource identifier of the system, prompting a re-editing request address;

and judging whether the sixth segment information is an operator, if the sixth segment information is the operator, prompting to finish the analysis of the request address, and if the sixth segment information is not the operator, prompting to re-edit the request address.

3. The method according to claim 1 or 2, wherein the receiving and resolving the request address comprises:

if the number of the separation identifiers in the request address is 4, sequentially acquiring 5 pieces of segment information, and respectively recording the 5 pieces of segment information as eleventh segment information to fifteenth segment information;

judging whether the eleventh segmentation information is a domain name, if so, executing a step of judging whether the twelfth segmentation information is a system name character string, and if not, prompting a re-editing request address for the domain name;

judging whether the twelfth segmentation information is a system name character string, if so, executing a step of judging whether the thirteenth segmentation information is a system version number character, and if not, prompting a re-editing request address;

judging whether the thirteenth sectional information is a system version number character string, if the thirteenth sectional information is the system version number character string, executing a step of judging whether the fourteenth sectional information is a resource identifier of the system, and if the thirteenth sectional information is not the system version number character string, prompting a re-editing request address;

judging whether the fourteenth segmentation information is a resource identifier of the system, if so, executing a step of judging whether the fifteenth segmentation information is an operator, and if not, prompting a re-editing request address;

and judging whether the fifteenth segmentation information is an operational character, if so, acquiring the resolution information of the request address, and if not, prompting to re-edit the request address.

4. The method according to claim 1, wherein after acquiring the editing content corresponding to the editing instruction, adjusting the resource correspondence of the system according to the editing content, obtaining and storing the adjusted system resource, the method further comprises:

5. The method according to claim 2, wherein the receiving a request address, counting the number of the separation identifiers in the request address, comprises:

6. A service request distribution apparatus, comprising:

the resource obtaining unit is used for obtaining a system with a version corresponding to the analysis information and the resource of the system according to the analysis information of the request address;

the resource editing unit is used for acquiring editing content corresponding to the editing instruction if the editing instruction of the system resource is detected, correspondingly adjusting the system resource according to the editing content, and obtaining and storing the adjusted system resource;

the acquiring a system of a version corresponding to the resolution information and a resource of the system according to the resolution information of the request address includes: establishing an initial system environment according to the analysis information of the request address; configuring the initial system environment according to the system of the version corresponding to the analysis information to obtain the current system environment; and acquiring resources of the system corresponding to the analysis information, and deploying the logic codes included in the resources of the system in the current system environment.

7. The service request distribution apparatus according to claim 6, wherein the access request parsing unit includes:

the statistical unit is used for receiving the request address and statistically acquiring the number of the separation identifiers in the request address;

a first sequence number allocation unit, configured to obtain 6 pieces of segment information in sequence if the number of the separation identifiers in the request address is 5, and record the 6 pieces of segment information as first segment information to sixth segment information respectively;

a first segmentation judging unit, configured to judge whether the first segmentation information is a domain name, execute a step of judging whether the second segmentation information is a company name identification string if the first segmentation information is the domain name, and prompt a re-editing request address if the first segmentation information is not the domain name;

a second segmentation judging unit, configured to judge whether the second segmentation information is a company name identification character string, execute a step of judging whether the third segmentation information is a system name character string if the second segmentation information is the company name identification character string, and prompt a re-editing request address if the second segmentation information is not the company name identification character string;

a third section judging unit, configured to judge whether the third section information is a system name string, execute a step of judging whether the fourth section information is a system version number string if the third section information is the system name string, and prompt a re-editing request address if the third section information is not the system name string;

a fourth segmentation judging unit, configured to judge whether the fourth segmentation information is a system version number character string, execute a step of judging whether the fifth segmentation information is a resource identifier of the system if the fourth segmentation information is the system version number character string, and prompt a re-editing request address if the fourth segmentation information is not the system version number character string;

a fifth segmentation judging unit, configured to judge whether the fifth segmentation information is a resource identifier of the system, execute a step of judging whether the sixth segmentation information is an operator if the fifth segmentation information is the resource identifier of the system, and prompt a re-edit request address if the fifth segmentation information is not the resource identifier of the system;

and the sixth segmentation judging unit is used for judging whether the sixth segmentation information is an operator, finishing the analysis of the request address if the sixth segmentation information is the operator, and re-editing the request address if the sixth segmentation information is not the operator.

8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the service request distribution method according to any one of claims 1 to 5 when executing the computer program.

9. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a processor, causes the processor to execute the service request distribution method according to any one of claims 1 to 5.