[asterisk-bugs] [Asterisk 0012556]: [patch] Realtime queue callers

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12556 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12556
Category:                   Applications/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 114874 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-30-2008 06:23 CDT
Last Modified:              04-30-2008 11:10 CDT
====================================================================== 
Summary:                    [patch] Realtime queue callers
Description: 
This patch adds new realtime family for queue callers. app_queue will do a
realtime store for new caller, and destroy for one left. 

This allows better monitoring of queue callers from multiple clients at
same time, as there is no need for caching of AMI commands, all is kept in
Realtime, and multiple clients are handled by database engine.


====================================================================== 

---------------------------------------------------------------------- 
 atis - 04-30-08 11:10  
---------------------------------------------------------------------- 
The problem with AMI is that it needs queue locking, and throwing 100 such
requests per second is quite a load for Asterisk. However MySQL deals with
this great.

My point for this is - to have current state of queues accessible by any
application, anytime. For future I have current queue member state and
channel state in realtime database (but I haven't cleaned up patches yet).
So this way amount of monitoring clients is limited only by database
capabilities.

The need for this in first place was caching problems with simultaneous
requests for channel/queue status and locking problems. For example, if I
query channel/queue information once per second, chances that Asterisk will
run into deadlock or crash increases.

Plus this feature isn't active unless enabled by adding realtime family,
so it won't affect users who don't need that. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-30-08 11:10  atis           Note Added: 0086215                          
======================================================================