Yate Design - Revision history

Monica: /* Engine */

2015-11-13T11:32:56Z

‎Engine

2015-11-13T11:32:34Z

‎Engine

2015-11-13T11:17:03Z

2015-11-13T11:03:25Z

2013-11-04T11:35:59Z

2012-12-05T18:00:53Z

‎Modules

2012-11-15T12:07:55Z

‎Modules

2012-11-15T12:05:16Z

2012-11-15T12:01:44Z

2012-11-15T11:36:55Z

@@ Line 20: / Line 20: @@
 The engine holds the base C++ classes of Yate and connects together all components.
-See the [[http://yate.null.ro/docs/|Yate C++ API]] here.
+See the [http://yate.null.ro/docs/|Yate C++ API] here.
 ===Modules===

@@ Line 19: / Line 19: @@
 ===Engine===
-The engine holds the base C++ classes of Yate and connects together all components. There is a [[Yate_architecture|diagram]] showing how all components interact.
+The engine holds the base C++ classes of Yate and connects together all components.
 ===Modules===

@@ Line 2: / Line 2: @@
 The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simple as possible and adding functionality as needed allows one to find the best balance between desired functionality, performance and stability.
-The architecture of Yate is based on a [[Messages|message passing]] system. The architecture can be divided into four main parts as you can see bellow.
+The architecture of Yate is based on a [[Messages|message passing]] system. The architecture can be divided into four main parts as you can see bellow:
-−
-Yate's four main components are:
 *   '''Core''' - generic classes like String, Thread, Socket, Mutex

← Older revision		Revision as of 11:03, 13 November 2015
Line 3:		Line 3:

	The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into four main parts as you can see bellow.		The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into four main parts as you can see bellow.
		+
		+	Yate's four main components are:
		+
		+	* '''Core''' - generic classes like String, Thread, Socket, Mutex
		+	* '''Message Engine''' - message related classes Message, Engine, Plugin
		+	* '''Telephony Engine''' - telephony related classes like Driver, Channel
		+	* '''Yate Modules''' - modules of Yate are equal no matter if they are telephony or routing or anything else related, because of the message passing system.
		+
		+	The most important aspect of Yate is its message-passing system. Modules are passing around messages among them. This allows us to have a bigger flexibility than with plain functions, mainly because messages in Yate can have an arbitrary number of parameters, and can be sent to more than one module by changing the priority.
		+
		+	[[File:yate-architecture.png]]

	===Core ===		===Core ===

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

@@ Line 14: / Line 14: @@
 ===Modules===
-Most real functionality is provided by [[Modules|modules]] loaded at runtime. These can be dynamical libraries loaded as plugins in the engine or external applications started by a specific module ([[External Module|extmodule]]) that allows them to talk to the engine and other modules.
+Most real functionality is provided by [[Modules|modules]] loaded at runtime. Modules are dynamic libraries loaded as plugins in the engine or external applications started by a specific module ([[External Module|extmodule]]) that allows them to talk to the engine and other modules.
 ===Messages===

← Older revision		Revision as of 12:05, 15 November 2012
Line 1:		Line 1:
−

	The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simple as possible and adding functionality as needed allows one to find the best balance between desired functionality, performance and stability.		The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simple as possible and adding functionality as needed allows one to find the best balance between desired functionality, performance and stability.

← Older revision		Revision as of 12:01, 15 November 2012
Line 2:		Line 2:

	The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simple as possible and adding functionality as needed allows one to find the best balance between desired functionality, performance and stability.		The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simple as possible and adding functionality as needed allows one to find the best balance between desired functionality, performance and stability.
−

	The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into four main parts as you can see bellow.		The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into four main parts as you can see bellow.

← Older revision		Revision as of 11:36, 15 November 2012
Line 4:		Line 4:


−	The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into 4 main parts as you can see bellow.	+	The architecture of Yate is based on a [[Messages\|message passing]] system. The architecture can be divided into four main parts as you can see bellow.

	===Core ===		===Core ===