A queue of message is a technology of programming used for the communication of interprocessus or the communication of waiter - with-waiter. In English, one speaks about “ Message-Oriented Middleware ” or “ Mom ”.

Overall picture

The queues of message provide standardized asynchronous connections. The purpose of they are that the shipper and the receiver of the message are not constrained to expect one the other. Messages placed in the queue are stored, until the recipient research. The shipper does not have to await that the receiver starts to treat its message, it station his information and can pass to another thing.

Many achievements of queues are created for the internal needs for the operating systems. They are essential for synchronization or work Multitâche of the process.

Other achievements of queue allow a communication between various computing systems, connecting several applications, or several operating systems. These systems of synchronization of messages provide typically a functionality of Persistance to make sure that the messages are not lost in the event of failure of the system. One speaks about Intergiciel directed message.

Use

In a typical implementation of tail of message, an interface manager would install and configure a Intergiciel directed message (a manager of queues), and would define a queue of message identified.

An application would be recorded then by means of a software routine which “would listen to” messages placed on the queue.

A second application would be connected then to this queue and would transfer a message.

The software of manager of queues would store the message until the application of reception is connected, and requires the message on standby. The application in reception would treat this message then in a suitable way.

Synchronous against asynchronous

Several of the protocols of transmissions, more largely known and in service lately, are synchronous of nature. The most obvious example is the protocol HTTP.

In a synchronous model, the interacting systems send a request and put answer on standby. In much of situations that seems reasonable (For example, a user sends a request for a Web page, then awaits an answer).

However, there are other situations for which it is not suitable. For example, if an application wishes to inform the others that an event occur, but does not want to await an answer. Another example is in the case of the subscribed systems as a publicator/, where a publicatrice application “publishes” information for all the others. In these two examples it would not be acceptable for the shipper of information to have to await the answer of a recipient “ broken down ”.

Commercial products

• [[MQ Series]] of IBM.
• MSMQ of Microsoft.

Random links:

Tourmont | Demography of Montenegro | Christian of Saxony-Merseburg | List Russian companies | Bandial (people)