CN106888218A - Message treatment method, device, client and service end - Google Patents
Message treatment method, device, client and service end Download PDFInfo
- Publication number
- CN106888218A CN106888218A CN201710214614.3A CN201710214614A CN106888218A CN 106888218 A CN106888218 A CN 106888218A CN 201710214614 A CN201710214614 A CN 201710214614A CN 106888218 A CN106888218 A CN 106888218A
- Authority
- CN
- China
- Prior art keywords
- message
- request message
- service end
- feedback
- redis
- 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.)
- Pending
Links
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/133—Protocols for remote procedure calls [RPC]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a kind of message treatment method, device, client and service end.Wherein, the method includes：Request message for asking far call is sent as intermediate transmission media to service end using a Redis queues；The feedback message fed back after service end is processed request message is received as intermediate transmission media using the 2nd Redis queues.By the present invention, Redis queues are solved in correlation technique as the intermediate transmission media between client and service end, realize that RPC has treatment complexity, the low technical problem of efficiency.Reach and realized that RPC treatment is simple, efficient purpose.
Description
Technical field
The present invention relates to network technique field, in particular to a kind of message treatment method, device, client and clothes
Business end.
Background technology
Remote procedure call (Remote Procedure Call, referred to as RPC) pattern is a visitor for Distributed Calculation
Family end/server mode, sends one and performs some procedure requests by user end to server, and service end receives request, uses
The parameter that client is provided, to calculate and return result to client after completing.RPC allows there is provided a transparent mechanism and uses
Person calls the method for remote service as local, convenient Distributed Services, Distributed Calculation, the remote service of building is called
Deng.The realization of RPC contains agreement formulation, network transmission, message distribution etc..
Realize that the framework of RPC has gRPC, Thrift, Dubbo at present, these frameworks are all relatively independent huge too fat to move, and
And need additionally mounted deployment.If starting from scratch realization, need treatment complex network communication issue, group of networks bag to unpack again,
Service availability problem etc..
Therefore, in the related art, realize that RPC has treatment complexity, the low problem of efficiency.For above-mentioned problem, mesh
It is preceding not yet to propose effective solution.
The content of the invention
A kind of message treatment method, device, client and service end are the embodiment of the invention provides, at least to solve correlation
In technology, realize that RPC has treatment complexity, the low technical problem of efficiency.
A kind of one side according to embodiments of the present invention, there is provided message treatment method, including：Using a Redis
Queue sends the request message for asking far call as intermediate transmission media to service end；Using the 2nd Redis queues
The feedback message fed back after the service end is processed the request message is received as intermediate transmission media.
Alternatively, sent for asking to the service end as intermediate transmission media using a Redis queues
The request message of far call includes：In the case where the service end is for multiple, use is carried in the request message
In the identification information for identifying the service end, using multiple Redis queues as intermediate transmission media to multiple service ends
Transmitted in parallel is used to ask the request message of far call.
Alternatively, sent for asking to the service end as intermediate transmission media using a Redis queues
The request message of far call includes：The request message is packaged into the form including following information：The service end
Title, the described long-range method of request, ask far call parameter, the sequence number of the request message；After encapsulating
Request message sequence chemical conversion character string；Request message after serializing is sent to described using the rpush methods of Redis
One Redis queues, for being sent to the service end by a Redis queues.
Alternatively, the service end is received to the request as intermediate transmission media using the 2nd Redis queues
The feedback message that message is fed back after being processed includes：The anti-of the service end feedback is read from the 2nd Redis queues
Feedback message；By the feedback message unserializing into the form including following information：The title of the first Redis queues, institute
State the title of the 2nd Redis queues, the service end request message is processed after result phase, the service end
Result after processing the request message, the sequence of the request message included described in the request message
Number；The corresponding result of the far call is obtained according to the feedback message after unserializing.
According to another aspect of the present invention, there is provided a kind of message treatment method, including：Made using a Redis queues
For intermediate transmission media receives the request message for asking far call that client sends；At the request message
Feedback message is obtained after reason；Disappeared to feedback described in the client feedback as intermediate transmission media using the 2nd Redis queues
Breath.
Alternatively, fed back to described in the client feedback as intermediate transmission media using the 2nd Redis queues
Message includes：In the case where the client is for multiple, carried in the feedback message for identifying the client
Identification information, the feedback message is fed back using multiple 2nd Redis queues as intermediate transmission media to multiple client.
Alternatively, the feedback message is obtained after processing the request message to be included：Will be from a Redis
The request message unserializing read in queue obtains the message of the form for including following information：The title of service end, please
The described long-range method asked, asks the parameter of far call, the sequence number of the request message；Message from after unserializing
The described long-range method of middle read requests, asks the parameter of far call, obtains alignment processing result；By the result
It is packaged into the feedback message of the form including following information：The title of the first Redis queues, the 2nd Redis queues
Title, the service end request message is processed after result phase, the service end is to the request message
Result after being processed, the sequence number of the request message included described in the request message.
According to an aspect of the present invention, there is provided a kind of message processing apparatus, including：First sending module, for using
First Redis queues send the request message for asking far call as intermediate transmission media to service end；First receives
Module, for using the 2nd Redis queues as intermediate transmission media receive the service end to the request message at
The feedback message fed back after reason.
Alternatively, first sending module, is additionally operable in the case where the service end is for multiple, the request message
In carry identification information for identifying the service end, using multiple Redis queues as intermediate transmission media to
Multiple service end transmitted in parallel are used to ask the request message of far call.
Alternatively, first sending module includes：First encapsulation unit, for by the request message be packaged into including
The form of following information：The title of the service end, the described long-range method of request asks the parameter of far call, described
The sequence number of request message；First ray unit, for the request message sequence after encapsulation to be melted into character string；First sends
Unit, for the request message after serializing to be sent into a Redis queues using the rpush methods of Redis, is used for
The service end is sent to by a Redis queues.
Alternatively, first receiver module includes：First reading unit, for reading from the 2nd Redis queues
Take the feedback message of the service end feedback；First unserializing unit, for by the feedback message unserializing into including
The form of following information：The title of the first Redis queues, the title of the 2nd Redis queues, the service end is to institute
State the result phase after request message is processed, the service end request message is processed after result,
The sequence number of the request message included described in the request message；Obtaining unit, for anti-after according to unserializing
Feedback message obtains the corresponding result of the far call.
According to another aspect of the present invention, there is provided a kind of client, including：Device described in any of the above-described.
According to an aspect of the present invention, there is provided a kind of message processing apparatus, including：Second receiver module, for using
First Redis queues receive the request message for asking far call that client sends as intermediate transmission media；Treatment
Module, for processing the request message after obtain feedback message；Feedback module, for using the 2nd Redis queues
As intermediate transmission media to feedback message described in the client feedback.
Alternatively, the feedback module, is additionally operable to, in the case where the client is for multiple, be taken in the feedback message
With the identification information for identifying the client, using multiple 2nd Redis queues as intermediate transmission media to multiple
Feedback message described in client feedback.
Alternatively, the processing module includes：Second unserializing unit, for will be from a Redis queues
The request message unserializing for reading obtains the message of the form for including following information：The title of service end, the institute of request
Long-range method is stated, the parameter of far call, the sequence number of the request message is asked；Second reading unit, for from inverted sequence
The described long-range method of read requests in message after rowization, asks the parameter of far call, obtains alignment processing result；The
Two encapsulation units, the feedback message for the result to be packaged into the form including following information：First Redis
The title of queue, the title of the 2nd Redis queues, the service end request message is processed after result shape
State, the service end request message is processed after result, what is included described in the request message is described
The sequence number of request message.
According to an aspect of the present invention, there is provided a kind of service end, including：Device described in any of the above-described.
A kind of further aspect of the invention, there is provided message handling system, including：Client described above, on
Shown service end is stated, and is used to transmit message as the intermediate transmission media between the client and the service end
Redis clusters.
A kind of further aspect of the invention, there is provided storage medium, the storage medium includes the program of storage, its
In, described program performs the message treatment method described in above-mentioned any one.
A kind of further aspect of the invention, there is provided processor, the processor is used for operation program, wherein, institute
The message treatment method described in above-mentioned any one is performed when stating program operation.
In embodiments of the present invention, using Redis queues as the middle biography between the client and the service end
Defeated medium, solves in correlation technique, realizes that RPC has treatment complexity, the low technical problem of efficiency.Reach and realized at RPC
Reason is simple, efficient purpose.
Brief description of the drawings
Accompanying drawing described herein is used for providing a further understanding of the present invention, constitutes the part of the application, this hair
Bright schematic description and description does not constitute inappropriate limitation of the present invention for explaining the present invention.In the accompanying drawings：
Fig. 1 is the flow chart of message treatment method one according to embodiments of the present invention；
Fig. 2 is the flow chart of message treatment method two according to embodiments of the present invention；
Fig. 3 is the configuration diagram of RPC according to embodiments of the present invention；
Fig. 4 is the form schematic diagram of the request message of RPC clients according to embodiments of the present invention；
Fig. 5 is the form schematic diagram of the results messages that RPC service end according to embodiments of the present invention returns；
Fig. 6 is the message processing flow-chart at RPC service end according to embodiments of the present invention；
Fig. 7 is the flow chart of the Message Processing of the RPC clients for providing according to embodiments of the present invention；
Fig. 8 is the structured flowchart of message processing apparatus one according to embodiments of the present invention；
Fig. 9 is the preferred structure block diagram of the first sending module 82 in message processing apparatus one according to embodiments of the present invention；
Figure 10 is the preferred structure block diagram of the first receiver module 84 in message processing apparatus one according to embodiments of the present invention；
Figure 11 is the structured flowchart of client according to embodiments of the present invention；
Figure 12 is the structured flowchart of message processing apparatus two according to embodiments of the present invention；
Figure 13 is the preferred structure block diagram of processing module 124 in message processing apparatus two according to embodiments of the present invention；
Figure 14 is the structured flowchart of service end according to embodiments of the present invention；
Figure 15 is the structured flowchart of message handling system according to embodiments of the present invention.
Specific embodiment
In order that those skilled in the art more fully understand the present invention program, below in conjunction with the embodiment of the present invention
Accompanying drawing, is clearly and completely described to the technical scheme in the embodiment of the present invention, it is clear that described embodiment is only
The embodiment of a part of the invention, rather than whole embodiments.Based on the embodiment in the present invention, ordinary skill people
The every other embodiment that member is obtained under the premise of creative work is not made, should all belong to the model of present invention protection
Enclose.
It should be noted that term " first ", " in description and claims of this specification and above-mentioned accompanying drawing
Two " it is etc. for distinguishing similar object, without for describing specific order or precedence.It should be appreciated that so using
Data can exchange in the appropriate case, so as to embodiments of the invention described herein can with except illustrating herein or
Order beyond those of description is implemented.Additionally, term " comprising " and " having " and their any deformation, it is intended that cover
Lid is non-exclusive to be included, for example, the process, method, system, product or the equipment that contain series of steps or unit are not necessarily limited to
Those steps or unit clearly listed, but may include not list clearly or for these processes, method, product
Or other intrinsic steps of equipment or unit.
According to embodiments of the present invention, there is provided a kind of embodiment of the method for message treatment method, it is necessary to explanation, attached
The step of flow of figure is illustrated can perform in the such as one group computer system of computer executable instructions, though also,
So logical order is shown in flow charts, but in some cases, can be with shown different from order execution herein
Or the step of description.
Fig. 1 is the flow chart of message treatment method one according to embodiments of the present invention, as shown in figure 1, the method is included such as
Lower step：
Step S102, is sent for asking long-range tune as intermediate transmission media using a Redis queues to service end
Request message；
Step S104, using the 2nd Redis queues as intermediate transmission media receive service end to request message at
The feedback message fed back after reason.
By above-mentioned steps, in client-side, using Redis queues as the intermediate conveyor between client and service end
Medium, because Redis queues are used as a kind of memory database of performance efficiency, with efficiently reading and writing, storage and transmission disappear
The function of breath, therefore, solve in correlation technique, realize that RPC has treatment complexity, the low technical problem of efficiency.Reality is reached
Existing RPC treatment is simple, efficient purpose.
To accelerate the transmission of message, it is used for being sent to service end as intermediate transmission media using a Redis queues
When asking the request message of far call, can be by the way of multiple service ends carry out concurrent processing.It is many i.e. in service end
The identification information for identifying service end is carried in the case of individual, in request message, using multiple Redis queue conducts
Intermediate transmission media is used to ask the request message of far call to multiple service end transmitted in parallel.
Relative in correlation technique, it is necessary to encapsulate much information in the message, using a Redis queues as centre
When transmission medium sends the request message for asking far call to service end, following packaged type can be used：Will request
Message is packaged into the form including following information：The title of service end, the long-range method of request asks the ginseng of far call
Number, the sequence number of request message；Request message sequence after encapsulation is melted into character string；Request message after serializing is used
The rpush methods of Redis are sent to a Redis queues, for being sent to service end by a Redis queues.Using envelope
The message of some needs is filled, relative to the packaged type of correlation technique, the traffic is effectively reduced.
Fed back being received after service end is processed request message as intermediate transmission media using the 2nd Redis queues
Feedback message when, the treatment for corresponding to, using corresponding processing mode：The reading service end feedback from the 2nd Redis queues
Feedback message；By feedback message unserializing into the form including following information：The title of the first Redis queues, second
The title of Redis queues, service end request message is processed after result phase, service end processed request message
Result afterwards, the sequence number of the request message that request message includes；Obtain remote according to the feedback message after unserializing
Journey calls corresponding result.
Fig. 2 is the flow chart of message treatment method two according to embodiments of the present invention, as shown in Fig. 2 the method is included such as
Lower step：
Step S202, the remote for asking of client transmission is received using a Redis queues as intermediate transmission media
The request message that journey is called；
Step S204, feedback message is obtained after processing request message；Passed as centre using the 2nd Redis queues
Defeated medium is to client feedback feedback message.
By above-mentioned steps, in service side, using Redis queues as the intermediate conveyor between client and service end
Medium, because Redis queues are used as a kind of memory database of performance efficiency, with efficiently reading and writing, storage and transmission disappear
The function of breath, therefore, solve in correlation technique, realize that RPC has treatment complexity, the low technical problem of efficiency.Reality is reached
Existing RPC treatment is simple, efficient purpose.
Equally, it is the transmission of quickening message, is using the 2nd Redis queues as intermediate transmission media to client feedback
During feedback message, it would however also be possible to employ multiple service ends carry out the mode of concurrent processing.For example, being multiple situations in client
Under, the identification information for identifying client is carried in feedback message, using multiple 2nd Redis queues as intermediate conveyor
Medium feeds back feedback message to multiple client.
Alternatively, when obtaining feedback message after processing request message, according to the difference of message content, can use
Different processing mode, it is for instance possible to use a kind of following processing mode：The request read from a Redis queues is disappeared
Breath unserializing obtains the message of the form for including following information：The title of service end, the long-range method of request, request is long-range
The parameter called, the sequence number of request message；The long-range method of read requests from the message after unserializing, request is long-range
The parameter called, obtains alignment processing result；Result is packaged into the feedback message of the form including following information：First
The title of Redis queues, the title of the 2nd Redis queues, service end request message is processed after result phase, service
Hold the result after processing request message, the sequence number of the request message that request message includes.It is few using encapsulation
The message for needing is measured, relative to the mode of a large amount of message of encapsulation of correlation technique, the traffic is effectively reduced.
Because Redis is the remarkable memory database of a performance, the read-write frequency per second more than 100K+ can be supported, often
Secondary read-write is all atomic operation, and also many Premium Features are usually used in actual items.Therefore, in above-described embodiment and
The new message treatment method that preferred embodiment is provided, based on increasing income, RPC frameworks are realized in memory database Redis queues,
High Availabitity is reached, high-performance is adapted to be used in the project for be deployed with Redis.
In above-described embodiment and preferred embodiment, mainly using the queue list of Redis offers as transfer source layer
Come what is realized.A message queue SERVER-Q is created first in Redis (to be carried in above-described embodiment and preferred embodiment
The Redis queues arrived)；The service end process of RPC is responsible for monitoring the new message of SERVER-Q；The client process of RPC is past
This SERVER-Q message queue sends message.Client also creates a queue CLIENT-Q (i.e. above-mentioned implementations in Redis
The 2nd Redis queues being previously mentioned in example and preferred embodiment) perform the knot returned after requesting method for receiving service end
Fruit message；When SERVER-Q is sent a message to, the message of encapsulation needs to take the ID of CLIENT-Q client；Service end according to
The message for receiving completes requesting method and obtains result, and results messages are sent into CLIENT-Q according to ID；Client is monitored
CLIENT-Q obtains result.
Wherein, service end and the client queue on Redis can create multiple, monitor the client and service end of queue
Can be multiple, the High Availabitity and high concurrent of message queue fully ensured that, to the encapsulation of self-defined message form inside Redis
So that we need not be concerned about package and the unpacking of bottom message, facilitate the high-performance treatments that program message sends and receives.
Below in conjunction with the accompanying drawings, the preferred embodiment for the present invention is illustrated.
Fig. 3 is the configuration diagram of RPC according to embodiments of the present invention, as shown in figure 3, the RPC includes three parts, its
In, left side Part I is the client of RPC, and centre is transmission medium Redis clusters, and the right is the service end of RPC.
Client part can open multiple transmission and ask and receive result, and client package request is sent to SERVER-
Q, reads result from CLIENT-Q.Client can create multiple CLIENT-Q for receive request.
Service end part is responsible for monitoring SERVER-Q message queues, reads designation method and parameter of the message in message
Perform, in sending the result to the CLIENT-Q that client is specified；Service end can open multiple monitoring SERVER-Q treatment and disappear
Breath, increases performance.
Redis clusters are independent services, as the message distribution intermediary of whole RPC, with High Availabitity, high performance spy
Point, safeguards the message queue that client and service end are created, and solve the problems, such as that multiple client competes queue.
Fig. 4 is the form schematic diagram of the request message of RPC clients according to embodiments of the present invention, as shown in figure 4, Src
Represent the CLIENT-Q message queue names that client is monitored；Dst represents that client is sent to the name of SERVER-Q message queues
Word；Method represents that RPC asks service end remote method name；Param is represented and is performed the incoming parameter of remote method；Id is represented
The sequence number of this message.
Fig. 5 is the form schematic diagram of the results messages that RPC service end according to embodiments of the present invention returns, as shown in figure 5,
Src represents the SERVER-Q message queue names that service end is monitored；Dst represents that service end result sends and wants CLIENT-Q message team
The name of row；Status represents that service end performs the result phase code of method；Result is obtained after representing service end execution method
Resultant content；Id represents that client sends the ID of request message.
Fig. 6 is the message processing flow-chart at RPC service end according to embodiments of the present invention, as shown in fig. 6, the flow includes
Following steps：
S601, service end is connected to Redis；
S602, service end creates a SERVER-Q message queue in Redis, disappears for receiving RPC client requests
Breath；
Here is service end circulating treatment procedure.
S603, service end reads SERVER-Q message queues using the blpop/lpop orders of Redis, if message then
Return to of queue foremost；If returning to sky immediately without message lpop, blpop is to block current process, it is also possible to
One blocking time timeout of configuration.
S604, service end reads a character string message, message unserializing into message object example is obtained (Src,
Dst, Method, Param, Id) form request message object.
S605, service end reads Method and Param from request message, is performed using Param parameters local
Method, obtains result.
Implementing result is packaged into results messages form (Src, Dst, Status, Result, Id) by S606, service end.Src
The name of SERVER-Q is filled out, the Src names that Dst is filled out in request message, Status fills out this implementing result state, Result fills out this
The content of secondary result, the Id that Id is filled out in solicited message.
S607, character string is melted into by results messages object sequence.
S608, the message queue that Src in request message is specified is sent to by the message after serializing using rpush
CLIENT-Q。
S603 to S608 is cyclic process, and the message for reading SERVER-Q queues is processed, and result is sent to
CLIENT-Q。
Fig. 7 is the flow chart of the Message Processing of the RPC clients for providing according to embodiments of the present invention, as shown in fig. 7, the stream
Journey comprises the following steps：
S701, the upper Redis of client connection.
S702 to S704 is the process for sending request.
S702, client will ask a far call, by the local name for monitoring CLIENT-Q, service end SERVER-Q
Name, long-range method, required parameter, the sequence number of this message be packaged into request message format (Src, Dst, Method, Param,
Id)。
Request message object sequence is melted into character string by S703, client.
Message after serializing is sent to SERVER-Q by S704, client using the rpush methods of Redis.
S705, client reads a results messages using blpop/lpop from CLIENT-Q.If message is then returned
Go back to queue foremost one；If returning to sky immediately without message lpop, blpop is to block current process, it is also possible to matched somebody with somebody
Put a blocking time timeout.
S706, after client reads a character string message, results messages object is deserialized as by message, and form is
(Src、Dst、Status、Result、Id)。
S707, client process results messages object.
S705 to S707 is the process for receiving results messages.
Client send message and receive message can be an asynchronous process (after i.e. client sends request, it is not necessary to
Hang-up waits for the arrival of news return, and period can perform other operations), or synchronization process (after i.e. client sends request,
Hang-up waits for the arrival of news return, and period not can perform other operations), flexible programming as needed.
By above-described embodiment and preferred embodiment, following technique effect can be realized：
1) high efficiency：The queue of the offer of memory database Redis is relied on, readwrite performance is high；Redis shields bottom communication
Details, without consider message send subpackage and unpacking, directly process application layer messages, this ensure RPC client and service
End can quickly send and receive message by queue.
2) message format is succinct：The traffic more than HTTP (Hyper Text Transfer Protocol,
Referred to as HTTP) it is few, increase system processing power.
3) security：By the rpush order write queues of Redis, the blpop/lpop orders of Redis (are removed and returned
The head element commands of queue) read queue be thread-safe, solve multi-client race problem under distributed environment.
4) it is expansible：The service end and client of RPC can open up any number of queue, message content on Redis
In Src, Dst, Id ensure message correctly transmit, extremely easily extension.
5) high concurrent：The client and service end of RPC can be multiple concurrent, accelerate message and send and Message Processing.
6) High Availabitity：Rely on Redis and cluster is disposed using master-slave mode, master machine is delayed machine, and master machine is switched to from machine.
There is network failure in client and service end connection Redis, and reconnecting message will not also lose.
According to embodiments of the present invention, a kind of device embodiment of message processing apparatus is additionally provided, Fig. 8 is according to the present invention
The structured flowchart of the message processing apparatus one of embodiment, as shown in figure 8, the device includes：First sending module 82 and first connects
Module 84 is received, the device is illustrated below.
First sending module 82, is used for for being sent to service end as intermediate transmission media using a Redis queues
Ask the request message of far call；First receiver module 84, is connected to above-mentioned first sending module 82, for using second
Redis queues receive the feedback message fed back after service end is processed request message as intermediate transmission media.
Alternatively, first sending module 82, is additionally operable to, in the case where service end is for multiple, be carried in request message
Identification information for identifying service end, using multiple Redis queues as intermediate transmission media to multiple service ends simultaneously
Row sends the request message for asking far call.
Fig. 9 is the preferred structure block diagram of the first sending module 82 in message processing apparatus one according to embodiments of the present invention,
As shown in figure 9, first sending module 82 includes：First encapsulation unit 92, the transmitting element of First ray unit 94 and first
96, first sending module 82 is illustrated below.
First encapsulation unit 92, for request message to be packaged into the form including following information：The title of service end, please
The long-range method asked, asks the parameter of far call, the sequence number of request message；First ray unit 94, is connected to
The first encapsulation unit 92 is stated, for the request message sequence after encapsulation to be melted into character string；First transmitting element 96, is connected to
First ray unit 94 is stated, for the request message after serializing to be sent into first using the rpush methods of Redis
Redis queues, for being sent to service end by a Redis queues.
Figure 10 is the preferred structure block diagram of the first receiver module 84 in message processing apparatus one according to embodiments of the present invention,
As shown in Figure 10, first receiver module 84 includes：First reading unit 102, the first unserializing unit 104 and obtaining unit
106, first receiver module 84 is illustrated below.
First reading unit 102, for the feedback message of the reading service end feedback from the 2nd Redis queues；First is anti-
Serialization unit 104, is connected to above-mentioned first reading unit 102, for by feedback message unserializing into including following information
Form：The title of the first Redis queues, the title of the 2nd Redis queues, service end request message is processed after knot
Fruit state, service end request message is processed after result, the sequence number of the request message that request message includes；
Obtaining unit 106, is connected to above-mentioned first unserializing unit 104, for obtaining remote according to the feedback message after unserializing
Journey calls corresponding result.
Figure 11 is the structured flowchart of client according to embodiments of the present invention, and as shown in figure 11, the client 110 includes upper
State the message processing apparatus 1 of any one.
Figure 12 is the structured flowchart of message processing apparatus two according to embodiments of the present invention, as shown in figure 12, the device bag
Include：Second receiver module 122, processing module 124 and feedback module 126, illustrate to the device below.
Second receiver module 122, for receiving what client sent as intermediate transmission media using a Redis queues
Request message for asking far call；Processing module 124, is connected to above-mentioned second receiver module 122, for disappearing to request
Breath obtains feedback message after being processed；Feedback module 126, above-mentioned processing module 124 is connected to, for using the 2nd Redis
Queue is as intermediate transmission media to client feedback feedback message.
Alternatively, above-mentioned feedback module 126, is additionally operable to, in the case where client is for multiple, be carried in feedback message
Identification information for identifying client, it is anti-to multiple client as intermediate transmission media using multiple 2nd Redis queues
Feedback feedback message.
Figure 13 is the preferred structure block diagram of processing module 124 in message processing apparatus two according to embodiments of the present invention, such as
Shown in Figure 13, the processing module 124 includes：Second unserializing unit 132, the second reading unit 134 and the second encapsulation unit
136, the processing module 124 is illustrated below.
Second unserializing unit 132, for the request message unserializing read from a Redis queues to be obtained
The message of the form including following information：The title of service end, the long-range method of request asks the parameter of far call, please
Seek the sequence number of message；Second reading unit 134, is connected to above-mentioned second unserializing unit 132, for from after unserializing
Message in read requests long-range method, ask far call parameter, obtain alignment processing result；Second encapsulation unit
136, above-mentioned second reading unit 134 is connected to, the feedback for result to be packaged into the form including following information disappears
Breath：The title of the first Redis queues, the title of the 2nd Redis queues, service end request message is processed after result shape
State, service end request message is processed after result, the sequence number of the request message that request message includes.
Figure 14 is the structured flowchart of service end according to embodiments of the present invention, as shown in figure 14, the service end 140, including：
The message processing apparatus 1 of any of the above-described.
Figure 15 is the structured flowchart of message handling system according to embodiments of the present invention, as shown in figure 15, the Message Processing
System 150, including：Above-mentioned client 110, above-mentioned shown service end 140, and as between client and service end
Intermediate transmission media is used to transmit the Redis clusters 152 of message.
In embodiments of the present invention, a kind of storage medium is additionally provided, storage medium includes the program of storage, wherein, journey
Sequence is used to perform the program code of following steps：Sent to service end as intermediate transmission media using a Redis queues and used
In the request message of request far call；Service end is received using the 2nd Redis queues as intermediate transmission media to disappear request
The feedback message that breath feeds back after being processed.
Alternatively, program is additionally operable to perform the program code of following steps：Using a Redis queues as intermediate conveyor
Medium is sent for asking the request message of far call to include to service end：In the case where service end is for multiple, request disappears
The identification information for identifying service end is carried in breath, using multiple Redis queues as intermediate transmission media to many
Individual service end transmitted in parallel is used to ask the request message of far call.
Alternatively, program is additionally operable to perform the program code of following steps：Using a Redis queues as intermediate conveyor
Medium is sent for asking the request message of far call to include to service end：Request message is packaged into including following information
Form：The title of service end, the long-range method of request asks the parameter of far call, the sequence number of request message；Will encapsulation
Request message sequence chemical conversion character string afterwards；Request message after serializing is sent to first using the rpush methods of Redis
Redis queues, for being sent to service end by a Redis queues.
Alternatively, program is additionally operable to perform the program code of following steps：Using the 2nd Redis queues as intermediate conveyor
Medium receives the feedback message fed back after service end is processed request message to be included：Clothes are read from the 2nd Redis queues
The feedback message of business end feedback；By feedback message unserializing into the form including following information：The name of the first Redis queues
Claim, the title of the 2nd Redis queues, service end request message is processed after result phase, service end is to request message
Result after being processed, the sequence number of the request message that request message includes；Disappeared according to the feedback after unserializing
Breath obtains the corresponding result of far call.
In embodiments of the present invention, a kind of storage medium is additionally provided, storage medium includes the program of storage, wherein, journey
Sequence is used to perform the program code of following steps：Client is received using a Redis queues as intermediate transmission media to send
The request message for asking far call；Feedback message is obtained after processing request message；Using the 2nd Redis teams
Row are as intermediate transmission media to client feedback feedback message.
Alternatively, program is additionally operable to perform the program code of following steps：Using the 2nd Redis queues as intermediate conveyor
Medium includes to client feedback feedback message：In the case where client is for multiple, carried for identifying in feedback message
The identification information of client, is disappeared as intermediate transmission media using multiple 2nd Redis queues to multiple client feedback feedback
Breath.
Alternatively, program is additionally operable to perform the program code of following steps：Fed back after processing request message
Message includes：The form that the request message unserializing read from a Redis queues obtains including following information is disappeared
Breath：The title of service end, the long-range method of request asks the parameter of far call, the sequence number of request message；From antitone sequence
The long-range method of read requests in message after change, asks the parameter of far call, obtains alignment processing result；Treatment is tied
Fruit is packaged into the feedback message of the form including following information：The title of the first Redis queues, the title of the 2nd Redis queues,
Service end request message is processed after result phase, service end request message is processed after result, please
Seek the sequence number of the request message that message includes.
In embodiments of the present invention, a kind of processor is additionally provided, processor is used for operation program, wherein, program operation
The program code of Shi Zhihang following steps：Sent for asking to service end as intermediate transmission media using a Redis queues
Seek the request message of far call；Service end is received using the 2nd Redis queues as intermediate transmission media to enter request message
The feedback message fed back after row treatment.
Alternatively, the program code of following steps is also performed when program is run：Passed as centre using a Redis queues
Defeated medium is sent for asking the request message of far call to include to service end：In the case where service end is for multiple, request
The identification information for identifying service end is carried in message, using multiple Redis queues as intermediate transmission media to
Multiple service end transmitted in parallel are used to ask the request message of far call.
Alternatively, the program code of following steps is also performed when program is run：Passed as centre using a Redis queues
Defeated medium is sent for asking the request message of far call to include to service end：Request message is packaged into including following information
Form：The title of service end, the long-range method of request asks the parameter of far call, the sequence number of request message；Will envelope
Request message sequence chemical conversion character string after dress；Request message after serializing is sent to using the rpush methods of Redis
One Redis queues, for being sent to service end by a Redis queues.
Alternatively, the program code of following steps is also performed when program is run：Passed as centre using the 2nd Redis queues
Defeated medium receives the feedback message fed back after service end is processed request message to be included：Read from the 2nd Redis queues
The feedback message of service end feedback；By feedback message unserializing into the form including following information：The name of the first Redis queues
Claim, the title of the 2nd Redis queues, service end request message is processed after result phase, service end is to request message
Result after being processed, the sequence number of the request message that request message includes；Disappeared according to the feedback after unserializing
Breath obtains the corresponding result of far call.
In embodiments of the present invention, a kind of processor is additionally provided, processor is used for operation program, wherein, program operation
The program code of Shi Zhihang following steps：The use that client sends is received as intermediate transmission media using a Redis queues
In the request message of request far call；Feedback message is obtained after processing request message；Made using the 2nd Redis queues
It is intermediate transmission media to client feedback feedback message.
Alternatively, the program code of following steps is also performed when program is run：Passed as centre using the 2nd Redis queues
Defeated medium includes to client feedback feedback message：In the case where client is for multiple, carried for marking in feedback message
Know the identification information of client, fed back to multiple client as intermediate transmission media using multiple 2nd Redis queues
Message.
Alternatively, the program code of following steps is also performed when program is run：Obtained after processing request message anti-
Feedback message includes：The request message unserializing read from a Redis queues is obtained including the form of following information
Message：The title of service end, the long-range method of request asks the parameter of far call, the sequence number of request message；From inverted sequence
The long-range method of read requests in message after rowization, asks the parameter of far call, obtains alignment processing result；Will treatment
Result is packaged into the feedback message of the form including following information：The title of the first Redis queues, the name of the 2nd Redis queues
Claim, service end request message is processed after result phase, service end request message is processed after result,
The sequence number of the request message that request message includes.
The embodiments of the present invention are for illustration only, and the quality of embodiment is not represented.
In the above embodiment of the present invention, the description to each embodiment all emphasizes particularly on different fields, and does not have in certain embodiment
The part of detailed description, may refer to the associated description of other embodiment.
In several embodiments provided herein, it should be understood that disclosed technology contents, can be by other
Mode is realized.Wherein, device embodiment described above is only schematical, the division of such as unit, can be one kind
Division of logic function, can there is other dividing mode when actually realizing, such as multiple units or component can combine or can
To be integrated into another system, or some features can be ignored, or not perform.It is another, it is shown or discussed each other
Coupling or direct-coupling or communication connection can be the INDIRECT COUPLING or communication connection of unit or module by some interfaces,
Can be electrical or other forms.
The unit illustrated as separating component can be or may not be physically separate, be shown as unit
Part can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple units
On.Some or all of unit therein can be according to the actual needs selected to realize the purpose of this embodiment scheme.
In addition, during each functional unit in each embodiment of the invention can be integrated in a processing unit, it is also possible to
It is that unit is individually physically present, it is also possible to which two or more units are integrated in a unit.Above-mentioned integrated list
Unit can both be realized in the form of hardware, it would however also be possible to employ the form of SFU software functional unit is realized.
If integrated unit, can to realize in the form of SFU software functional unit and as independent production marketing or when using
To store in a computer read/write memory medium.Based on such understanding, technical scheme substantially or
Saying all or part of the part or technical scheme contributed to prior art can be embodied in the form of software product
Out, computer software product storage is in a storage medium, including some instructions are used to so that a computer equipment
(can be personal computer, server or network equipment etc.) performs all or part of step of each embodiment method of the invention
Suddenly.And foregoing storage medium includes：USB flash disk, read-only storage (ROM, Read-Only Memory), random access memory
(RAM, Random Access Memory), mobile hard disk, magnetic disc or CD etc. are various can be with the medium of store program codes.
The above is only the preferred embodiment of the present invention, it is noted that come for those skilled in the art
Say, under the premise without departing from the principles of the invention, can also make some improvements and modifications, these improvements and modifications also should be regarded as
Protection scope of the present invention.
Claims (19)
1. a kind of message treatment method, it is characterised in that including：
Request message for asking far call is sent as intermediate transmission media to service end using a Redis queues；
Receive anti-after the service end is processed the request message as intermediate transmission media using the 2nd Redis queues
The feedback message of feedback.
2. method according to claim 1, it is characterised in that be situated between as intermediate conveyor using a Redis queues
Matter is sent for asking the request message of far call to include to the service end：
In the case where the service end is for multiple, the mark for identifying the service end is carried in the request message and is believed
Breath, is used to ask far call as intermediate transmission media using multiple Redis queues to multiple service end transmitted in parallel
Request message.
3. method according to claim 1, it is characterised in that be situated between as intermediate conveyor using a Redis queues
Matter is sent for asking the request message of far call to include to the service end：
The request message is packaged into the form including following information：The title of the service end, request it is described long-range
Method, asks the parameter of far call, the sequence number of the request message；
Request message sequence after encapsulation is melted into character string；
Request message after serializing is sent to a Redis queues using the rpush methods of Redis, for passing through
The first Redis queues are sent to the service end.
4. method according to claim 3, it is characterised in that be situated between as intermediate conveyor using the 2nd Redis queues
Matter receives the feedback message fed back after the service end is processed the request message to be included：
The feedback message of the service end feedback is read from the 2nd Redis queues；
By the feedback message unserializing into the form including following information：The title of the first Redis queues, described
The title of two Redis queues, the service end request message is processed after result phase, the service end is to institute
The result after request message is processed is stated, the sequence number of the request message included described in the request message；
The corresponding result of the far call is obtained according to the feedback message after unserializing.
5. a kind of message treatment method, it is characterised in that including：
Disappeared as the request for asking far call that intermediate transmission media receives client transmission using a Redis queues
Breath；
Feedback message is obtained after processing the request message；
Using the 2nd Redis queues as intermediate transmission media to feedback message described in the client feedback.
6. method according to claim 5, it is characterised in that be situated between as intermediate conveyor using the 2nd Redis queues
Matter includes to feedback message described in the client feedback：
In the case where the client is for multiple, the mark for identifying the client is carried in the feedback message and is believed
Breath, the feedback message is fed back using multiple 2nd Redis queues as intermediate transmission media to multiple client.
7. method according to claim 5, it is characterised in that the feedback is obtained after processing the request message
Message includes：
The request message unserializing read from a Redis queues is obtained including the form of following information
Message：The title of service end, the described long-range method of request asks the parameter of far call, the sequence of the request message
Number；
The described long-range method of read requests from the message after unserializing, asks the parameter of far call, is corresponded to
Result；
The result is packaged into the feedback message of the form including following information：The title of the first Redis queues,
The title of the 2nd Redis queues, the service end request message is processed after result phase, the service
Hold the result after processing the request message, the sequence of the request message included described in the request message
Row number.
8. a kind of message processing apparatus, it is characterised in that including：
First sending module, for sending remote for asking to service end as intermediate transmission media using a Redis queues
The request message that journey is called；
First receiver module, asks for receiving the service end as intermediate transmission media using the 2nd Redis queues to described
The feedback message fed back after asking message to be processed.
9. device according to claim 8, it is characterised in that first sending module, is additionally operable in the service end
In the case of for multiple, the identification information for identifying the service end is carried in the request message, using multiple first
Redis queues are used to ask the request message of far call as intermediate transmission media to multiple service end transmitted in parallel.
10. device according to claim 8, it is characterised in that first sending module includes：
First encapsulation unit, for the request message to be packaged into the form including following information：The title of the service end,
The described long-range method of request, asks the parameter of far call, the sequence number of the request message；
First ray unit, for the request message sequence after encapsulation to be melted into character string；
First transmitting element, for the request message after serializing to be sent into described first using the rpush methods of Redis
Redis queues, for being sent to the service end by a Redis queues.
11. devices according to claim 10, it is characterised in that first receiver module includes：
First reading unit, the feedback message for reading the service end feedback from the 2nd Redis queues；
First unserializing unit, for by the feedback message unserializing into including following information form：Described first
The title of Redis queues, the title of the 2nd Redis queues, after the service end is processed the request message
Result phase, the service end request message is processed after result, include described in the request message
The request message sequence number；
Obtaining unit, for obtaining the corresponding result of the far call according to the feedback message after unserializing.
A kind of 12. clients, it is characterised in that including：Device any one of claim 8 to 11.
A kind of 13. message processing apparatus, it is characterised in that including：
Second receiver module, for using a Redis queues as intermediate transmission media reception client transmission for asking
Seek the request message of far call；
Processing module, for processing the request message after obtain feedback message；
Feedback module, for being disappeared to feedback described in the client feedback as intermediate transmission media using the 2nd Redis queues
Breath.
14. devices according to claim 13, it is characterised in that the feedback module, be additionally operable to be in the client
In the case of multiple, the identification information for identifying the client is carried in the feedback message, using multiple second
Redis queues feed back the feedback message as intermediate transmission media to multiple client.
15. devices according to claim 14, it is characterised in that the processing module includes：
Second unserializing unit, for the request message unserializing read from a Redis queues to be obtained
To the message of the form including following information：The title of service end, the described long-range method of request asks the ginseng of far call
Number, the sequence number of the request message；
Second reading unit, for the described long-range method of the read requests from the message after unserializing, request is long-range to adjust
Parameter, obtains alignment processing result；
Second encapsulation unit, the feedback message for the result to be packaged into the form including following information：Described
The title of one Redis queues, the title of the 2nd Redis queues, after the service end is processed the request message
Result phase, the service end request message is processed after result, described in the request message wrap
The sequence number of the request message for including.
A kind of 16. service ends, it is characterised in that including：Device any one of claim 13 to 15.
A kind of 17. message handling systems, it is characterised in that including：Client described in claim 12, shown in claim 16
Service end, and be used to transmit the Redis of message as the intermediate transmission media between the client and the service end
Cluster.
18. a kind of storage mediums, it is characterised in that the storage medium includes the program of storage, wherein, described program right of execution
Profit requires the message treatment method described in any one in 1 to 7.
19. a kind of processors, it is characterised in that the processor is used for operation program, wherein, right of execution when described program is run
Profit requires the message treatment method described in any one in 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710214614.3A CN106888218A (en) | 2017-04-01 | 2017-04-01 | Message treatment method, device, client and service end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710214614.3A CN106888218A (en) | 2017-04-01 | 2017-04-01 | Message treatment method, device, client and service end |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106888218A true CN106888218A (en) | 2017-06-23 |
Family
ID=59182282
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710214614.3A Pending CN106888218A (en) | 2017-04-01 | 2017-04-01 | Message treatment method, device, client and service end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106888218A (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107241351A (en) * | 2017-07-14 | 2017-10-10 | 广州四三九九信息科技有限公司 | A kind of RPC communication method based on Redis |
| CN107566297A (en) * | 2017-09-05 | 2018-01-09 | 荷花科技（北京）有限公司 | Internet of Things service processing method and system |
| CN108984316A (en) * | 2018-06-15 | 2018-12-11 | 广州视源电子科技股份有限公司 | It is a kind of for the method, apparatus of distributed data processing, electronic equipment and computer storage medium |
| CN109040094A (en) * | 2018-08-21 | 2018-12-18 | 郑州云海信息技术有限公司 | A kind of method and system for realizing asynchronous RPC based on RabbitMQ |
| CN110119324A (en) * | 2019-05-15 | 2019-08-13 | 苏州浪潮智能科技有限公司 | A kind of RPC system and its communication means based on redis |
| CN110493303A (en) * | 2019-07-03 | 2019-11-22 | 招联消费金融有限公司 | Business data processing system and method |
| CN110611687A (en) * | 2018-06-15 | 2019-12-24 | 武汉安天信息技术有限责任公司 | Remote procedure call implementation method based on Redis and related device |
| CN110661849A (en) * | 2019-08-30 | 2020-01-07 | 中国人民财产保险股份有限公司 | Request processing method and device, electronic equipment and storage medium |
| CN110750349A (en) * | 2019-10-26 | 2020-02-04 | 武汉中海庭数据技术有限公司 | Distributed task scheduling method and system |
| CN111198773A (en) * | 2019-12-31 | 2020-05-26 | 上海汇付数据服务有限公司 | Message-based application communication method and device |
| CN111629278A (en) * | 2020-05-22 | 2020-09-04 | 新石器慧通（北京）科技有限公司 | Image transmission method, image transmission device, movable platform, server and storage medium |
| CN112286698A (en) * | 2019-07-23 | 2021-01-29 | 北京地平线机器人技术研发有限公司 | Remote procedure call method and device and remote procedure call execution method |
| CN112433870A (en) * | 2020-12-01 | 2021-03-02 | 网易（杭州）网络有限公司 | Data calling method and device, computer readable storage medium and electronic equipment |
| WO2021121370A1 (en) * | 2019-12-20 | 2021-06-24 | 北京金山云网络技术有限公司 | Message loss detection method and apparatus for message queue |
| CN114553928A (en) * | 2021-12-31 | 2022-05-27 | 完美世界(重庆)互动科技有限公司 | Business processing method and device, electronic equipment and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102111419A (en) * | 2011-03-07 | 2011-06-29 | 浙江大学 | Message middleware-based client automatic reconnection method |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN103914339A (en) * | 2014-04-09 | 2014-07-09 | 百度在线网络技术（北京）有限公司 | Server management system and server management method |
| CN104486330A (en) * | 2014-12-11 | 2015-04-01 | 上海爱数软件有限公司 | Two-way communication system based on remote procedure calls (RPCs) |
| US20160055233A1 (en) * | 2014-08-25 | 2016-02-25 | Ca, Inc. | Pre-join tags for entity-relationship modeling of databases |
| CN106201739A (en) * | 2016-06-29 | 2016-12-07 | 上海浦东发展银行股份有限公司信用卡中心 | A kind of remote invocation method of Storm based on Redis |
-
2017
- 2017-04-01 CN CN201710214614.3A patent/CN106888218A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102111419A (en) * | 2011-03-07 | 2011-06-29 | 浙江大学 | Message middleware-based client automatic reconnection method |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN103914339A (en) * | 2014-04-09 | 2014-07-09 | 百度在线网络技术（北京）有限公司 | Server management system and server management method |
| US20160055233A1 (en) * | 2014-08-25 | 2016-02-25 | Ca, Inc. | Pre-join tags for entity-relationship modeling of databases |
| CN104486330A (en) * | 2014-12-11 | 2015-04-01 | 上海爱数软件有限公司 | Two-way communication system based on remote procedure calls (RPCs) |
| CN106201739A (en) * | 2016-06-29 | 2016-12-07 | 上海浦东发展银行股份有限公司信用卡中心 | A kind of remote invocation method of Storm based on Redis |
Non-Patent Citations (1)
| Title |
|---|
| OSCHINA: "通过Redis实现RPC远程方法调用", 《开源中国》 * |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107241351A (en) * | 2017-07-14 | 2017-10-10 | 广州四三九九信息科技有限公司 | A kind of RPC communication method based on Redis |
| CN107566297A (en) * | 2017-09-05 | 2018-01-09 | 荷花科技（北京）有限公司 | Internet of Things service processing method and system |
| CN108984316A (en) * | 2018-06-15 | 2018-12-11 | 广州视源电子科技股份有限公司 | It is a kind of for the method, apparatus of distributed data processing, electronic equipment and computer storage medium |
| CN110611687A (en) * | 2018-06-15 | 2019-12-24 | 武汉安天信息技术有限责任公司 | Remote procedure call implementation method based on Redis and related device |
| CN109040094A (en) * | 2018-08-21 | 2018-12-18 | 郑州云海信息技术有限公司 | A kind of method and system for realizing asynchronous RPC based on RabbitMQ |
| CN110119324A (en) * | 2019-05-15 | 2019-08-13 | 苏州浪潮智能科技有限公司 | A kind of RPC system and its communication means based on redis |
| CN110493303A (en) * | 2019-07-03 | 2019-11-22 | 招联消费金融有限公司 | Business data processing system and method |
| CN110493303B (en) * | 2019-07-03 | 2022-04-01 | 招联消费金融有限公司 | Service data processing system and method |
| CN112286698A (en) * | 2019-07-23 | 2021-01-29 | 北京地平线机器人技术研发有限公司 | Remote procedure call method and device and remote procedure call execution method |
| CN110661849A (en) * | 2019-08-30 | 2020-01-07 | 中国人民财产保险股份有限公司 | Request processing method and device, electronic equipment and storage medium |
| CN110750349A (en) * | 2019-10-26 | 2020-02-04 | 武汉中海庭数据技术有限公司 | Distributed task scheduling method and system |
| WO2021121370A1 (en) * | 2019-12-20 | 2021-06-24 | 北京金山云网络技术有限公司 | Message loss detection method and apparatus for message queue |
| CN111198773A (en) * | 2019-12-31 | 2020-05-26 | 上海汇付数据服务有限公司 | Message-based application communication method and device |
| CN111198773B (en) * | 2019-12-31 | 2024-03-29 | 上海汇付支付有限公司 | Message-based application communication method and device |
| CN111629278A (en) * | 2020-05-22 | 2020-09-04 | 新石器慧通（北京）科技有限公司 | Image transmission method, image transmission device, movable platform, server and storage medium |
| CN111629278B (en) * | 2020-05-22 | 2022-07-26 | 新石器慧通（北京）科技有限公司 | Image transmission method, image transmission device, movable platform, server and storage medium |
| CN112433870A (en) * | 2020-12-01 | 2021-03-02 | 网易（杭州）网络有限公司 | Data calling method and device, computer readable storage medium and electronic equipment |
| CN114553928A (en) * | 2021-12-31 | 2022-05-27 | 完美世界(重庆)互动科技有限公司 | Business processing method and device, electronic equipment and medium |
| CN114553928B (en) * | 2021-12-31 | 2024-04-16 | 完美世界(重庆)互动科技有限公司 | Service processing method and device, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106888218A (en) | Message treatment method, device, client and service end | |
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| JP7112919B2 (en) | Smart device task processing method and device | |
| CN107332787A (en) | A kind of message distributing method and device | |
| CN106850402A (en) | The transmission method and device of message | |
| US20050262269A1 (en) | System and method for information handling system PCI express advanced switching | |
| CN108009028A (en) | Message treatment method, device, equipment and computer-readable recording medium | |
| US20190068728A1 (en) | Systems, apparatuses, and methods for intelligent network communication and engagement | |
| CN108600300A (en) | Daily record data processing method and processing device | |
| CN105190530B (en) | Transmit the graph data of Hardware Render | |
| CN109254854A (en) | Asynchronous invoking method, computer installation and storage medium | |
| CN109995801A (en) | A kind of method for message transmission and device | |
| CN108124007A (en) | The method and apparatus of message data real-time Transmission | |
| CN108829868A (en) | data display method and device, storage medium and electronic device | |
| CN104811403B (en) | Group list processing method, apparatus and group table configuration unit based on open flows | |
| CN105207886A (en) | Instant messaging (IM) message sending and display methods, IM message sending and display devices, and IM message system | |
| CN105471700B (en) | A kind of methods, devices and systems of Message Processing | |
| CN107241387A (en) | The processing method of request of data, apparatus and system | |
| CN106156146B (en) | Method and device for allocating anonymous nicknames of group sessions | |
| CN106572135A (en) | Network request processing method and device | |
| CN106844763A (en) | A kind of method represented to the Internet media file formula of modifying and its device | |
| CN107968798A (en) | A kind of network management resources label acquisition method, cache synchronization method, apparatus and system | |
| CN105530321B (en) | Method, client, server and system for accessing equipment by browser client | |
| CN105933352B (en) | Method of data synchronization, client and system between client-based server | |
| CN106408793B (en) | A kind of Service Component sharing method and system suitable for ATM business |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170623 |
|
| RJ01 | Rejection of invention patent application after publication |