CN110351350B - Client request processing method and system based on multi-server docking and electronic equipment - Google Patents
Client request processing method and system based on multi-server docking and electronic equipment Download PDFInfo
- Publication number
- CN110351350B CN110351350B CN201910578932.7A CN201910578932A CN110351350B CN 110351350 B CN110351350 B CN 110351350B CN 201910578932 A CN201910578932 A CN 201910578932A CN 110351350 B CN110351350 B CN 110351350B
- Authority
- CN
- China
- Prior art keywords
- request
- service
- classification
- server
- client
- 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.)
- Expired - Fee Related
Links
- 238000003032 molecular docking Methods 0.000 title claims abstract description 19
- 238000003672 processing method Methods 0.000 title claims abstract description 8
- 238000000034 method Methods 0.000 claims abstract description 96
- 238000012545 processing Methods 0.000 claims abstract description 37
- 230000008569 process Effects 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 10
- 230000002194 synthesizing effect Effects 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 7
- 238000002054 transplantation Methods 0.000 abstract description 5
- 238000012805 post-processing Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 7
- 230000000694 effects Effects 0.000 description 6
- 235000014510 cooky Nutrition 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- 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/10—Protocols in which an application is distributed across nodes in the network
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a client request processing method and system based on multi-server docking, electronic equipment and a computer readable medium. The method adopts a method that different service IDs can be customized by a client to process the request of the corresponding server and automatically generate the corresponding server. After receiving the request at the client, the user sends the request to a specific server for processing according to different types of the server. Therefore, the invention can realize that the corresponding server is requested to be addressed for post-processing, and is convenient for later transplantation and modular development.
Description
Technical Field
The invention relates to the field of computer information processing, in particular to a client request processing method and system based on multi-server docking, electronic equipment and a computer readable medium.
Background
In a client/server architecture, it is common for multiple clients to receive multiple requests, which are then sent over a network to a server or servers. The request may be various and the server may be various. This random transmission of requests or server management can result in transmission confusion, code redundancy, and other adverse effects. In particular, when the server has a plurality of different functions, it is inconvenient for a developer to perform modular development or later migration.
In order to solve the problems in the prior art, the invention discloses a client request processing method, a client request processing system, electronic equipment and a computer readable medium based on multi-server docking. The method can be applied to application scenarios that a plurality of clients access a plurality of servers, or one client accesses a plurality of servers.
Disclosure of Invention
The invention aims to solve the problem that in the prior art, a user uses a single client or a plurality of clients to send a request to a plurality of servers. A client request processing method, a system, electronic equipment and a computer readable medium based on multi-server docking are provided. After receiving the request at the client, the user sends the request to a specific server for processing according to different types of the server. The method is convenient for modular development or later-stage transplantation, the codes are concise and clear, and the efficiency of information receiving and searching and the user experience level are greatly improved.
In order to solve the above technical problem, a first aspect of the present invention provides a method for processing a client request based on multi-server docking, including: receiving a request sent by a client through a basic network module, wherein the request is sent according to a request protocol and contains a service ID; realizing service ID through a factory method to create different server corresponding files; distributing the request to different servers through the basic network module based on the corresponding files of different servers; the server processes the request.
According to a preferred embodiment of the present invention, a classification table is set in the basic network module, and the requests sent by the clients each time are classified into different classes of service IDs according to the classification table.
According to a preferred embodiment of the invention, said implementing a service ID by means of a factory method further comprises implementing a specific network request in which said service ID is marked.
According to a preferred embodiment of the present invention, the distributing the request to the different servers by the infrastructure network module comprises: and automatically finding the corresponding server module through the service ID to realize decoupling.
According to a preferred embodiment of the present invention, the classification table is defined by the following method: normalizing the request sent by the client into a standard request; a standard request is defined to address the corresponding server module.
According to a preferred embodiment of the invention, the standard request is defined to address a unique corresponding server module.
According to a preferred embodiment of the present invention, the factory method implements the service ID, including the process of parsing, encoding, and synthesizing the service ID.
In order to solve the above technical problem, a second aspect of the present invention provides a client request processing system based on multi-server docking, including:
a basic network module for receiving the request sent by the client, wherein the request is sent according to the request protocol and contains the service ID, and distributing the request to different servers through the network module based on the corresponding files of different servers
A factory method implementation module for implementing the service ID by a factory method to create different corresponding files of the server;
at least one server for processing the request.
According to a preferred embodiment of the present invention, a classification table is set in the basic network module, and the requests sent by the clients each time are classified into different classes of service IDs according to the classification table.
According to a preferred embodiment of the invention, the factory method implementation module further comprises implementing a specific network request in which to mark the service ID.
According to a preferred embodiment of the present invention, the basic network module automatically finds a corresponding server by a service ID to implement decoupling.
According to a preferred embodiment of the invention, the classification table is defined by: and normalizing the request sent by the client into a standard request, wherein the standard request is defined as addressing a corresponding server module.
According to a preferred embodiment of the invention, a standard request is defined to address a unique corresponding server.
According to a preferred embodiment of the present invention, the factory method implements the service ID, including the process of parsing, encoding, and synthesizing the service ID.
In order to solve the above technical problem, a third aspect of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above method when executing the program.
In order to solve the above technical problem, a fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, the program being executable by a processor to implement the above method.
The invention adopts a method that different service IDs can be customized by the client to process the request of the corresponding server and automatically generate the corresponding server. After receiving the request at the client, the user sends the request to a specific server for processing according to different types of the server. In the period, the invention adopts a unique method of establishing different service corresponding files by classifying the standardized requests of the table and realizing the service ID by a factory method, and the network module automatically finds the corresponding service by the ID to realize the decoupling method. Therefore, the invention can realize that the corresponding server is requested to be addressed for post-processing, and is convenient for later transplantation and modular development.
Drawings
In order to make the technical problems solved by the present invention, the technical means adopted and the technical effects obtained more clear, the following will describe in detail the embodiments of the present invention with reference to the accompanying drawings. It is to be noted, however, that the drawings described below are only drawings of exemplary embodiments of the invention, from which other embodiments can be derived by those skilled in the art without inventive effort.
FIG. 1 is a flow chart illustrating a method for processing a client request based on multi-server docking according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating a client request processing system based on multi-server docking according to an embodiment of the present invention;
FIG. 3 is a block diagram of an exemplary embodiment of an electronic device in accordance with the present invention;
FIG. 4 is a flowchart illustrating a method for processing a client request based on multi-server docking according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of one computer-readable medium embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention may be embodied in many specific forms, and should not be construed as limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art.
The structures, properties, effects or other characteristics described in a certain embodiment may be combined in any suitable manner in one or more other embodiments, while still complying with the technical idea of the invention.
In the description of the specific embodiments, the details of construction, performance, effects, or other characteristics are set forth in order to provide a thorough understanding of the embodiments for one skilled in the art. However, it is not excluded that a person skilled in the art may implement the invention in a specific case without the above-described structures, performances, effects or other features.
The flow chart in the drawings is only an exemplary flow demonstration, and does not represent that all the contents, operations and steps in the flow chart are necessarily included in the scheme of the invention, nor does it represent that the execution is necessarily performed in the order shown in the drawings. For example, some operations/steps in the flowcharts may be divided, some operations/steps may be combined or partially combined, and the like, and the execution order shown in the flowcharts may be changed according to actual situations without departing from the gist of the present invention.
The block diagrams in the figures generally represent functional entities and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The same reference numerals denote the same or similar elements, components, or parts throughout the drawings, and thus, a repetitive description thereof may be omitted hereinafter. It will be further understood that, although the terms first, second, third, etc. may be used herein to describe various elements, components, or sections, these elements, components, or sections should not be limited by these terms. That is, these phrases are used only to distinguish one from another. For example, a first device may also be referred to as a second device without departing from the spirit of the present invention. Furthermore, the term "and/or", "and/or" is intended to include all combinations of any one or more of the listed items.
Fig. 1 shows a flowchart of a method for processing a client request based on multi-server docking according to an embodiment of the present invention. The method comprises the following steps:
s1, receiving a request sent by a client through a basic network module, wherein the request is sent according to a request protocol and contains a service ID; s2, realizing service ID through a factory method to create different server corresponding files; s3, distributing the request to different servers through the basic network module based on the corresponding files of different servers; s4, the server processes the request.
Specifically, a request protocol is first defined, and the request protocol is implemented. The request protocol is a protocol associated with the request. The request protocol may be a protocol that is conventional in the art, for example, the associated request protocol may include one or more of a web services interface, a Business Application Programming Interface (BAPI), or a remote function invocation (RFC) interface. In particular, XAFAPIBASEManager, XAFAPIMARAGErParamSourceDelegate, XAFAPIMARIAger, etc. By defining the request protocol, the request protocol is realized, and the security of the network and the access is enhanced.
The client then sends a request to the underlying network module, wherein the client has customized various different service ids (serviceids), the request being accompanied by the request protocol. The client sends the received request to the basic network module to be transmitted.
The following example details how the client can customize various different service IDs.
The client defines the received request as having a unique service ID by means of which it can be identified which request is, for example, by means of a URL (uniform resource locator) in the internet. Each service ID customized is specifically intended to correspond to one or more servers, i.e. in this sense request a specific data service. In particular, the service ID may also be a list of service IDs, which list is correspondingly directed by the service ID. In particular, the service ID determines the attributes of the received request. Customization or definition of service ID to subsequently classify received requests, address them to servers, process or operate upon.
Particularly, the method for customizing the service ID can immerse a cookie module in the basic network module, a first request received by the client is enabled to carry a first service ID value by using a cookie or other modes, the basic network module can easily determine the requirement of the user by reading the first service ID value, and the cookie is actually generated by the basic network module and then sent to the user equipment end, and the cookie is small information not exceeding 4kb, so that the basic network module can provide diversified services for the user by only transmitting a small amount of information in the process of carrying out various service for the user, and further the user experience is effectively improved.
Similarly, the second request received by the client carries the second service ID value through the cookie. The first request and the second request are different. Wherein the first service ID value may be the same as the second service ID value. Or the first service ID value may be different from the second service ID value. Similarly, the client also accepts a third request, a fourth request … …, which may or may not have the same or different corresponding service ID value.
Optionally, a classification table is set in the basic network module, and according to the classification table, the requests sent by the clients each time are classified into different classes of service IDs. The classification list may also be a classification list that classifies requests received by the client. The classification method is performed according to the category of the backend device, i.e. the backend server.
The following example details how the classification tables are defined.
The classification table comprises a classification list, wherein data such as classification codes, classification indexes and dimension codes are contained in the classification list. The request with the service ID information is decomposed into a dimension code, a classification code, and a classification index. And combining the dimension codes, the classification codes and the classification indexes to form an index dimension relation, and forming an index dimension relation table, namely a classification list, according to the index dimension relation. More specifically, the classification code is defined by relevance, the classification index is defined by priority, and the dimension code is defined by usage habit, which may all be defined or designed by a developer. And extracting the classification codes and the classification index combinations in the classification list, mapping the classification codes and the classification index combinations to the associated dimension codes respectively, acquiring an index dimension relation, and forming an index dimension relation table, namely the classification list.
Optionally, the classification table is defined by a method including normalizing the request sent by the client into a standard request, the standard request being defined as addressing a corresponding server module. Standard requests are defined to address a unique corresponding server module.
The following example is a method of normalizing to a standard request.
And a min-max standardized model is adopted to realize the normalization processing of various different requests. And addressing the corresponding server module according to the normalized data. In order to more accurately transmit the different requests to the target server, which is the server most suitable for handling the request.
Next, the service ID is implemented by a factory method to create a different server correspondence file. In particular, the plant process is XAFServiceFactory. The creation of the different services by ID may be implemented by a newServiceWithIdentifier.
Also included is implementing a specific network request in which the service ID is tagged.
The factory method realizes the service ID, and comprises the processes of analyzing, coding and synthesizing the service ID. Various different requests can be accurately matched with a service module or a server through identification and identification, and then are in butt joint, so that subsequent information processing is performed.
The following examples illustrate the plant process in detail.
Factory method (factory method), the factory method mode is equivalent to new for creating instance objects, developers of systems or running devices often need to generate instance objects according to Class, for example, Aa ═ new a (), the factory method mode is also used for creating instance objects, and greater expandability and least modification are brought to the systems. The factory pattern can dynamically decide which class to instantiate without knowing in advance which class to instantiate each time. The invention adopts a factory method to process the request, can realize classification, can realize greater expansibility and is convenient for modular development. When a certain type of request and a corresponding service module need to be selected or split, the method is simple and clear.
The following modes of the plant process are common:
1. simple factory method mode: also known as static factory method mode.
2. Factory method mode: also known as polymorphic plant patterns.
3. Abstract factory method schema: also known as a tool box mode.
Advantages of using the factory method model: if the initialization work done when creating an instance is not simply like assigning values, it may be a long section of code, which is not reasonable if it is also written into the constructor. If the initialization work is a long code segment, the work to be done is much, the work is loaded into a method, the principle of Java object-oriented is also existed, object-oriented packaging (Encapsulation) and allocation (deletion) tell developers to try to 'cut' the long code allocation into each segment, and then 'package' each segment again (reducing the coupling relation between the segments), thus dispersing the risk, and if the modification is needed later, only changing each segment. The developer then needs the Factory method schema to generate the object.
In particular, the plant method employs the following constructor:
by adopting the factory method, different requests can be used for realizing service IDs corresponding to different service modules, so that the method not only can accurately correspond and quickly react, but also is beneficial to modular development and later-stage transplantation, and is convenient for inquiry, screening and sorting.
Then, the request is distributed to different servers through the network module based on the corresponding files of the different servers. The server can be, for example, a fund service module, a wealth service module, and the like.
The network module automatically finds the corresponding server module through the service ID to realize decoupling.
Finally the server processes the request. The server is a backend device that may be configured to execute a software system or service. The service may be accessed to perform various processing requests and may return results of the processing for the requester associated with the processing request.
Those skilled in the art will appreciate that all or part of the steps for implementing the above-described embodiments are implemented as programs executed by data processing apparatuses (including computers), i.e., computer programs. When the computer program is executed, the method provided by the invention can be realized. Furthermore, the computer program may be stored in a computer readable storage medium, which may be a readable storage medium such as a magnetic disk, an optical disk, a ROM, a RAM, or a storage array composed of a plurality of storage media, such as a magnetic disk or a magnetic tape storage array. The storage medium is not limited to centralized storage, but may be distributed storage, such as cloud storage based on cloud computing.
Embodiments of systems of the present invention are described below, which may be used to perform method embodiments of the present invention. Details described in the system embodiments of the invention should be considered supplementary to the above-described method embodiments; reference is made to the above-described method embodiments for details not disclosed in the system embodiments of the invention.
FIG. 2 is a schematic diagram of a client request processing system based on multi-server docking according to an embodiment of the present invention. The system comprises:
the basic network module receives a request sent by a client, wherein the request is sent according to a request protocol and contains a service ID, and the request is distributed to different servers through the network module based on corresponding files of the different servers;
a factory method implementation module for implementing service ID by factory method to create different server corresponding files;
at least one server for processing the request.
Optionally, a classification table is set in the basic network module, and according to the classification table, the request sent by the client at each time is classified into different categories of service IDs.
Optionally, the factory method implementation module further comprises implementing a specific network request, in which request the service ID is marked.
Optionally, the network module automatically finds the corresponding server module by the service ID, so as to implement decoupling.
Optionally, the classification table is defined by: normalizing the request sent by the client into a standard request; a standard request is defined to address the corresponding server module.
Alternatively, a standard request is defined to address a unique corresponding server module.
Optionally, the factory method implements the service ID, including parsing, encoding, and synthesizing the service ID.
In the client request processing system based on multi-server docking according to this embodiment, the implementation principle and technical effect of the method for implementing client request processing based on multi-server docking by using the modules are the same as those of the related method embodiments, and reference may be made to the description of the related method embodiments in detail, which is not described herein again.
Those skilled in the art will appreciate that the modules in the above-described system embodiments may be distributed in the system as described, and that corresponding variations may be made in one or more systems other than the above-described embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
An embodiment of the electronic device of the invention is described below, which may be regarded as an implementation in physical form for the above-described embodiments of the method and system of the invention. Details described in the embodiments of the electronic device of the invention should be considered supplementary to the embodiments of the method or system described above; for details not disclosed in the embodiments of the electronic device of the invention, reference may be made to the above-described method or system embodiments.
Fig. 3 is a block diagram of an exemplary embodiment of an electronic device according to the present invention. The electronic device shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 3, the electronic device 310 of the exemplary embodiment is represented in the form of a general-purpose data processing device. The components of the electronic device 310 may include, but are not limited to: at least one processing unit 311, at least one memory unit 312, a bus 316 connecting different system components (including the memory unit 312 and the processing unit 311), a display unit 313, and the like.
The storage unit 312 stores a computer readable program, which may be a code of a source program or a read-only program. The program may be executed by the processing unit 311 to cause the processing unit 210 to perform the steps of various embodiments of the present invention. For example, the processing unit 311 may perform the steps as shown in fig. 1.
The storage unit 312 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)3121 and/or a cache storage unit 3122, and may further include a read only memory unit (ROM) 3123. The storage unit 312 can also include a program/utility 3124 having a set (at least one) of program modules 3125, such program modules 3125 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may comprise an implementation of a network environment.
The electronic device 310 may also communicate with one or more external devices 320 (e.g., a keyboard, a display, a network device, a bluetooth device, etc.), enable a user to interact with the electronic device 320 via the external devices 320, and/or enable the electronic device 310 to communicate with one or more other data processing devices (e.g., a router, a modem, etc.). Such communication may occur via input/output (I/O) interfaces 314, and may also occur via a network adapter 315 with one or more networks, such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet. The network adapter 315 may communicate with other modules of the electronic device 320 via the bus 316. It should be appreciated that although not shown, other hardware and/or software modules may be used in the electronic device 310, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Fig. 4 is a flowchart illustrating an operation of a method for processing a client request based on multi-server docking according to an embodiment of the present invention. The server takes fund service and financial service modules as examples, and schematically illustrates the whole process from protocol definition, request receiving, request sending, request processing to the server.
FIG. 5 is a schematic diagram of one computer-readable medium embodiment of the present invention. As shown in fig. 5, the computer program may be stored on one or more computer readable media. The computer readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The computer program, when executed by one or more data processing devices, enables the computer-readable medium to implement the above-described methods of the present invention, namely: a client request processing method, a system, electronic equipment and a computer readable medium based on multi-server docking are provided. After receiving the request at the client, the user sends the request to a specific server for processing according to different types of the server. The method is convenient for modular development or later stage transplantation, the codes are concise and clear, and the efficiency of information receiving and searching and the user experience level are greatly improved.
Through the description of the above embodiments, those skilled in the art will readily understand that the exemplary embodiments described in the present invention may be implemented by software, and may also be implemented by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a data processing device (which can be a personal computer, a server, or a network device, etc.) execute the above-mentioned method according to the present invention.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices (e.g., through the internet using an internet service provider).
In summary, the present invention can be implemented as a method, system, electronic device, or computer-readable medium that executes a computer program. Some or all of the functions of the present invention may be implemented in practice using a general-purpose data processing device such as a microprocessor or a Digital Signal Processor (DSP).
While the foregoing detailed description has described in detail certain embodiments of the invention with reference to certain specific aspects, embodiments and advantages thereof, it should be understood that the invention is not limited to any particular computer, virtual machine, or electronic device, as various general purpose machines may implement the invention. The invention is not to be considered as limited to the specific embodiments thereof, but is to be understood as being modified in all respects, all changes and equivalents that come within the spirit and scope of the invention.
Claims (10)
1. A client request processing method based on multi-server docking comprises the following steps:
receiving a request sent by a client through a basic network module, wherein the request is sent according to a request protocol and contains a unique service ID customized by the client to the received request;
setting a classification table in the basic network module, wherein the classification table comprises a classification list, decomposing a request with service ID information into a dimension code, a classification code and a classification index, combining the dimension code, the classification code and the classification index to form an index dimension relation, forming the classification list according to the index dimension relation, and classifying the request sent by each client into different classes of service IDs according to the classification table; defining a dimension code according to a using habit, defining a classification code according to relevance and defining a classification index according to priority;
realizing service ID by a factory method, analyzing, coding and synthesizing the service ID, matching and butting various different requests with a service module or a server through identification and identification to create different corresponding files of the server;
distributing the request to different servers through the basic network module based on the corresponding files of the different servers;
the server processes the request.
2. The method of claim 1, wherein:
and setting a classification table in the basic network module, and classifying the request sent by the client each time into different service IDs according to the classification table.
3. The method of claim 1, wherein:
the implementing a service ID by factory method further includes implementing a specific network request in which the service ID is tagged.
4. The method of claim 1, wherein:
the distributing the request to the different servers by the infrastructure network module comprises: and automatically finding the corresponding server module through the service ID to realize decoupling.
5. The method of claim 2, wherein:
the classification table is defined by the following method:
normalizing the request sent by the client into a standard request;
a standard request is defined to address the corresponding server module.
6. The method of claim 5, wherein:
standard requests are defined to address unique corresponding server modules.
7. The method according to any one of claims 1 to 6, wherein:
the factory method realizes the service ID, and comprises the processes of analyzing, coding and synthesizing the service ID.
8. A client request processing system based on multi-server docking, comprising:
the basic network module receives a request sent by a client, wherein the request is sent according to a request protocol and contains a unique service ID customized by the client to the received request; setting a classification table in the basic network module, wherein the classification table comprises a classification list, decomposing a request with service ID information into a dimension code, a classification code and a classification index, combining the dimension code, the classification code and the classification index to form an index dimension relation, forming the classification list according to the index dimension relation, and classifying the request sent by each client into different categories of service IDs according to the classification table; and distributing the request to different servers through the network module based on different server corresponding files; defining a dimension code according to a using habit, defining a classification code according to relevance and defining a classification index according to priority;
the factory method implementation module is used for implementing the service ID through a factory method, analyzing, coding and synthesizing the service ID, matching and butting various different requests with the service module or the server through identification and identification so as to create different corresponding files of the server;
at least one server for processing the request.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor, when executing the program, implements the method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which is executable by a processor to implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910578932.7A CN110351350B (en) | 2019-06-28 | 2019-06-28 | Client request processing method and system based on multi-server docking and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910578932.7A CN110351350B (en) | 2019-06-28 | 2019-06-28 | Client request processing method and system based on multi-server docking and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110351350A CN110351350A (en) | 2019-10-18 |
| CN110351350B true CN110351350B (en) | 2022-09-06 |
Family
ID=68177218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910578932.7A Expired - Fee Related CN110351350B (en) | 2019-06-28 | 2019-06-28 | Client request processing method and system based on multi-server docking and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110351350B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111273999B (en) * | 2020-01-20 | 2021-07-20 | 北京字节跳动网络技术有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106856434A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | The method and apparatus of access request conversion |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7092399B1 (en) * | 2001-10-16 | 2006-08-15 | Cisco Technology, Inc. | Redirecting multiple requests received over a connection to multiple servers and merging the responses over the connection |
| CN105607951A (en) * | 2015-12-17 | 2016-05-25 | 北京奇虎科技有限公司 | Method and device for processing data request and obtaining server information |
| CN106843895B (en) * | 2017-02-07 | 2020-05-19 | 上海网易小额贷款有限公司 | Method, system and readable storage medium for processing requests |
| US20180255144A1 (en) * | 2017-03-04 | 2018-09-06 | Wipro Limited | Method and system for providing spatial distribution of content to a user in real time |
| CN107426304A (en) * | 2017-07-06 | 2017-12-01 | 努比亚技术有限公司 | Method, system and the proxy server of interactive media resource |
| CN108052615B (en) * | 2017-12-15 | 2021-12-21 | 泰康保险集团股份有限公司 | Access request processing method, device, medium and electronic equipment |
| CN109246222A (en) * | 2018-09-21 | 2019-01-18 | 郑州云海信息技术有限公司 | service request processing method, device, system and computer readable storage medium |
-
2019
- 2019-06-28 CN CN201910578932.7A patent/CN110351350B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106856434A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | The method and apparatus of access request conversion |
Non-Patent Citations (1)
| Title |
|---|
| 简单工厂模式;一个博客id;《http://blog.sina.com.cn/s/blog_185268e880102xxvr.html》;20180729;正文第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110351350A (en) | 2019-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7483959B2 (en) | Method and system for extensible data gathering | |
| US7536409B2 (en) | Having a single set of object relational mappings across different instances of the same schemas | |
| US9772890B2 (en) | Sophisticated run-time system for graph processing | |
| US9363195B2 (en) | Configuring cloud resources | |
| AU2016302371B2 (en) | Building and managing data-processing attributes for modeled data sources | |
| US9400700B2 (en) | Optimized system for analytics (graphs and sparse matrices) operations | |
| US11403356B2 (en) | Personalizing a search of a search service | |
| US10885087B2 (en) | Cognitive automation tool | |
| US8417725B2 (en) | Consolidating related task data in process management solutions | |
| US20090030979A1 (en) | TUNABLE ENGINE AND PROGRAM PRODUCT FOR RESOLVING PREREQUISITES FOR CLIENT DEVICES IN AN OPEN SERVICE GATEWAY INITIATIVE (OSGi) FRAMEWORK | |
| US7457809B2 (en) | System and method for retrieving and analyzing data from a variety of different sources | |
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| JP2009054151A (en) | Communication message instance generation method, data instance generation method, communication message instance generation apparatus, and computer readable medium | |
| CN113625998B (en) | Request processing method and device | |
| CN110351350B (en) | Client request processing method and system based on multi-server docking and electronic equipment | |
| US7475090B2 (en) | Method and apparatus for moving data from an extensible markup language format to normalized format | |
| US20130191357A1 (en) | Managing multiple versions of enterprise meta-models using semantic based indexing | |
| CN111831320A (en) | Plug-in management method and device, electronic equipment and storage medium | |
| US20120136881A1 (en) | Exchanging data using data transformation | |
| US11449677B2 (en) | Cognitive hierarchical content distribution | |
| US12001458B2 (en) | Multi-cloud object store access | |
| US7567971B2 (en) | Generic symbol referencing mechanism | |
| US20200334256A1 (en) | Navigation paths between content items | |
| CN114416215A (en) | Function calling method and device | |
| KR20220129884A (en) | Multiple open OS access method and system in VDI environment |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20220906 |