[asterisk-bugs] [Asterisk 0009924]: Responses to Manager Commands Should Be Called 'Responses' and not 'Events'

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9924 
====================================================================== 
Reported By:                davetroy
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   9924
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 67990 
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             06-08-2007 15:43 CDT
Last Modified:              03-04-2008 17:13 CST
====================================================================== 
Summary:                    Responses to Manager Commands Should Be Called
'Responses' and not 'Events'
Description: 
In developing a new Ruby library for AMI, it became clear that separating
AMI Event handling from AMI Actions by using two sockets was a good idea. 
With this in place, it also became evident that there are several Manager
Actions which generate blocks called "Events", but which are not in fact
sent to Event subscribers.

This is because these "Event" responses are not in fact true Events
(utilizing the Eventing calls) but are really a string of Responses sent to
whatever user generated the matching "Action".

For this reason I propose changing these incorrectly-labeled "Event:"
blocks to "Response:" blocks.  This change also makes sense since objects
like SipPeers are ostensibly not "Events" and are not being sent as a
result of anything "happening" in the system.

Actions affected include: ZapShowChannels, SipShowPeers, Agents,
VoicemailUsers, Queues, QueueStatus, WaitEvent, Status, DBGet,
ListDialplan, ParkedCalls
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 03-04-08 17:13  
---------------------------------------------------------------------- 
The problem is that this destroys the nice 1:1 correspondence between
Actions and Responses.  The reason the Event is used is to keep a single
response for each Action and generate additional information as Events. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-08 17:13  Corydon76      Note Added: 0083377                          
======================================================================