[asterisk-bugs] [JIRA] (ASTERISK-21103) Stasis Core - Refactor the other event types onto the Stasis Core message bus

Jonathan Rose (JIRA) noreply at issues.asterisk.org
Fri May 3 13:11:38 CDT 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-21103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Rose updated ASTERISK-21103:
-------------------------------------

    Description: 
Once the Stasis Core API is finished, we need to begin refactoring current consumers/producers on the event subsystem to take advantage of it. Other issues cover the 'first class' object types; this issue is to take care of:

* {{-AST_EVENT_NETWORK_CHANGE-}}
* {{AST_EVENT_SECURITY}}
* {{-AST_EVENT_ACL_CHANGE-}}

There is a good chance that the appropriate message payload for these event types will be a JSON message that contains the information about how the item changed.

  was:
Once the Stasis Core API is finished, we need to begin refactoring current consumers/producers on the event subsystem to take advantage of it. Other issues cover the 'first class' object types; this issue is to take care of:

* {{AST_EVENT_NETWORK_CHANGE}}
* {{AST_EVENT_SECURITY}}
* {{-AST_EVENT_ACL_CHANGE-}}

There is a good chance that the appropriate message payload for these event types will be a JSON message that contains the information about how the item changed.

    
> Stasis Core - Refactor the other event types onto the Stasis Core message bus
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-21103
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21103
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/Stasis
>            Reporter: Matt Jordan
>            Assignee: Jonathan Rose
>              Labels: Asterisk12
>      Target Release: 12
>
>
> Once the Stasis Core API is finished, we need to begin refactoring current consumers/producers on the event subsystem to take advantage of it. Other issues cover the 'first class' object types; this issue is to take care of:
> * {{-AST_EVENT_NETWORK_CHANGE-}}
> * {{AST_EVENT_SECURITY}}
> * {{-AST_EVENT_ACL_CHANGE-}}
> There is a good chance that the appropriate message payload for these event types will be a JSON message that contains the information about how the item changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list