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

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=9924 
====================================================================== 
Reported By:                davetroy
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   9924
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0-beta5 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 67990 
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             06-08-2007 15:43 CDT
Last Modified:              04-01-2008 13:05 CDT
====================================================================== 
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 - 04-01-08 13:05  
---------------------------------------------------------------------- 
After careful consideration with other developers, we're going to close
this out with no action.  The reason is, it's purely a textual change, has
no real benefit, and would break almost every Manager application out there
for no good reason.  For this, and the reasons outlined before (breaking
1:1 correspondence between Actions and Responses), we're rejecting this
change. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-01-08 13:05  Corydon76      Note Added: 0084871                          
04-01-08 13:05  Corydon76      Assigned To              oej => Corydon76    
04-01-08 13:05  Corydon76      Status                   assigned => closed  
04-01-08 13:05  Corydon76      Resolution               open => won't fix   
======================================================================