Messages - Revision history

Moritz Orbach: /* Example of call.route message */ linked first appearance of call.route

2014-03-10T20:38:42Z

‎Example of call.route message: linked first appearance of call.route

2013-11-04T11:37:16Z

2013-11-04T11:36:43Z

2013-05-16T11:02:59Z

2013-05-16T11:01:38Z

2013-05-16T11:01:07Z

2013-05-16T11:00:47Z

2013-05-16T11:00:04Z

2013-05-16T10:59:08Z

2013-05-15T10:34:13Z

@@ Line 48: / Line 48: @@
 === Example of ''call.route'' message ===
-A very good example about how the message system works is the "call.route" message. <br>
+A very good example about how the message system works is the "[[call.route]]" message.
 ==== Generate the message====
 When a call comes in at some point, a messages is generated like this:

← Older revision		Revision as of 11:37, 4 November 2013
Line 129:		Line 129:
	* [[External Module]]		* [[External Module]]

−	[[Category:Programmers]] [[Category:Messages]]	+	[[Category:Programmers]] [[Category:Messages]] [[Category:Message handlers]] [[Category:Message queue]]

← Older revision		Revision as of 11:36, 4 November 2013
Line 128:		Line 128:
	* [[Yate Design]]		* [[Yate Design]]
	* [[External Module]]		* [[External Module]]
		+
		+	[[Category:Programmers]] [[Category:Messages]]

@@ Line 6: / Line 6: @@
 Messages can be dispatched or enqueued. Dispatching a message is done synchronously in the execution thread of the module that called dispatch. The execution of the module stops until answer is received. Enqueue is done asynchronously. The message is set in a queue and the execution thread continues without waiting for a response.
-Handlers are message hooks that allow a certain module to receive the message.
+Handlers are message hooks that allow a certain module to receive the message. Each module installs handlers for all the messages it needs to receive.
 ===How messages are processed===

@@ Line 6: / Line 6: @@
 Messages can be dispatched or enqueued. Dispatching a message is done synchronously in the execution thread of the module that called dispatch. The execution of the module stops until answer is received. Enqueue is done asynchronously. The message is set in a queue and the execution thread continues without waiting for a response.
-Handlers are messages hooks that allows a certain module to receive the message.
+Handlers are message hooks that allow a certain module to receive the message.
 ===How messages are processed===

@@ Line 4: / Line 4: @@
 [[File:yate-architecture.png]]
-Messages can be dispatched or enqueued. Dispatching a message is done synchronously in the execution thread of the module that called dispatch. The execution of the module stops until answer is received. Enqueue is done asynchronously. The messages is set in a queue and the execution thread continues without waiting for a response.
+Messages can be dispatched or enqueued. Dispatching a message is done synchronously in the execution thread of the module that called dispatch. The execution of the module stops until answer is received. Enqueue is done asynchronously. The message is set in a queue and the execution thread continues without waiting for a response.
 Handlers are messages hooks that allows a certain module to receive the message.