Messages in JS

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
In Yate, you can have access to any message. Only a handler must be installed.
+
From Javascript module (the same goes for external scripts) you can have access to all Yate's messages.
  
For example, for routing you need a handler installed for ''call.route'' message.
+
In order to receive a message you must install a handler.
 +
 
 +
You can also create, a custom MessageQueue, to avoid usage of internal Yate's message queue, if you need to handle a specific message, that takes too long to be processed by Yate.
  
In Javascript you have to install handler for ''MessageQueue'' message.
 
  
 
{|class="yate-table"
 
{|class="yate-table"
Line 9: Line 10:
 
|-
 
|-
 
|class="yate-content-right"|
 
|class="yate-content-right"|
<div class="bullet">&nbsp;</div><font class="yate-page-title">[[MessageQueue]]</font><br/>
+
* [[Install handler for using Yate's messages in Javascript]]
<div class="yate-page-desc">The MessageQueues is used to create a mechanism for organizing YATE's messages in different queues.</div>
+
How to install handler fot messages from Javascript.
 +
* [[MessageQueue]]
 +
The MessageQueue is a mechanism for organizing Yate's messages in different queues.
 
|}
 
|}
  
Line 18: Line 21:
 
* [[Messages]]
 
* [[Messages]]
 
* [[Javascript]]
 
* [[Javascript]]
 +
 +
[[Category:Javascript]] [[Category:Programmers]]

Latest revision as of 14:54, 1 November 2013

From Javascript module (the same goes for external scripts) you can have access to all Yate's messages.

In order to receive a message you must install a handler.

You can also create, a custom MessageQueue, to avoid usage of internal Yate's message queue, if you need to handle a specific message, that takes too long to be processed by Yate.


YATE's Messages in JavaScript

How to install handler fot messages from Javascript.

The MessageQueue is a mechanism for organizing Yate's messages in different queues.


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers