[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:              05-01-2008 07:07 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.


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

---------------------------------------------------------------------- 
 Corydon76 - 05-01-08 07:07  
---------------------------------------------------------------------- 
There are lots of interfaces that we "could" have, but there are a limited
number that we are willing to support.  Trying to use a database backend
for status support is not an interface that we really want to start
supporting, especially when there is a perfectly good interface (AMI) that
serves the same need.  You're right that the command does not exist now,
but that means that you may serve as a designer for a new command or set of
commands and decide what that command should look like and what information
the response will contain.

This is really a request for "support this new interface I dreamed up",
which is NOT appropriate for the bugtracker, anyway.  The fact that it
looks like and works off an existing interface is irrelevant -- realtime is
designed for configuration data, not for dissemination of status data.

If you would like to design the appropriate AMI command for querying queue
status, that is fine.  However, if you are not going down that road, this
issue will be closed. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-01-08 07:07  Corydon76      Note Added: 0086248                          
======================================================================