[asterisk-dev] [Code Review] 2389: Transition Device State usage to Stasis
opticron
reviewboard at asterisk.org
Mon Apr 1 12:07:27 CDT 2013
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2389/
-----------------------------------------------------------
(Updated April 1, 2013, 12:07 p.m.)
Review request for Asterisk Developers.
Changes
-------
Address David's comments.
Bugs: ASTERISK-21101
https://issues.asterisk.org/jira/browse/ASTERISK-21101
Repository: Asterisk
Description
-------
In the move from Asterisk's event system to Stasis, this makes distributed device state aggregation always-on, removes unnecessary task processors where possible, and collapses aggregate and non-aggregate states into a single cache for ease of retrieval. This also removes an intermediary step in device state aggregation.
Diffs (updated)
-----
trunk/apps/app_queue.c 384324
trunk/include/asterisk/devicestate.h 384324
trunk/include/asterisk/xmpp.h 384324
trunk/main/asterisk.c 384324
trunk/main/ccss.c 384324
trunk/main/devicestate.c 384324
trunk/main/pbx.c 384324
trunk/res/res_jabber.c 384324
trunk/res/res_xmpp.c 384324
trunk/tests/test_devicestate.c 384324
Diff: https://reviewboard.asterisk.org/r/2389/diff/
Testing
-------
This change was run against the queue integration tests, the generic_ccss test, the device_state_notification test, and the non_digium_state_change test with no ill effects.
Thanks,
opticron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130401/a03c4425/attachment.htm>
More information about the asterisk-dev
mailing list