[asterisk-dev] [Code Review]: Move Newexten and UserEvent AMI events to Stasis; adding JSON messages to stasis-core

[opticron]

> On March 18, 2013, 8:43 a.m., opticron wrote:
> > /trunk/main/manager_channels.c, line 237
> > <https://reviewboard.asterisk.org/r/2381/diff/4/?file=34691#file34691line237>
> >
> >     Instead of setting the precedent of using new variables to confer that more information be added to the AMI event, I suggest using an additional ast_str.  This additional ast_str can then be added to the channel state blob before being sent out.  This would also allow the Newexten event to use the same mechanism as the other channel state messages.
> 
> David Lee wrote:
>     I'm with you on using ast_str, but I'm less sure about using it for Newexten. There's a bit of extra logic, and you may have a single snapshot fire both a Newstate and Newexten at the same time.

On that same note, I guess it's possible that the others could overlap as well if a state message failed allocation and got skipped somewhere.


- opticron


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2381/#review8072
-----------------------------------------------------------


On March 18, 2013, 12:27 p.m., David Lee wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2381/
> -----------------------------------------------------------
> 
> (Updated March 18, 2013, 12:27 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> This patch started out simply as fixing the bouncing tests introduced
> in r382685, but required some other changes to give it a decent
> implementation.
> 
> To fix the bouncing tests, the UserEvent and Newexten AMI events
> needed to be refactored to dispatch via Stasis. Dispatching directly
> to AMI resulted in those events sometimes getting ahead of the
> associated Newchannel events, which would understandably confuse anyone.
> 
> I found that instead of creating a zillion different message types and
> structures associated with them, it would be preferable to define a
> message type that has a channel snapshot and a blob of structured data
> with a small bit of additional information. The JSON object model
> provides a very nice way of representing structured data, so I went
> with that.
> 
>  * Move JSON support from res_json.c to main/json.c
>    * Made libjansson-dev a required dependency
>  * Added an ast_channel_blob message type, which has a channel
>    snapshot and JSON blob of data.
>  * Changed UserEvent and Newexten events so that they are dispatched
>    via ast_channel_blob messages on the channel's topic.
>  * Got rid of the ast_channel_varset message; used ast_channel_blob
>    instead.
>  * Extracted the manager functions converting Stasis channel events to
>    AMI events into manager_channel.c.
> 
> 
> This addresses bug ASTERISK-21096.
>     https://issues.asterisk.org/jira/browse/ASTERISK-21096
> 
> 
> Diffs
> -----
> 
>   /trunk/CHANGES 383287 
>   /trunk/apps/app_userevent.c 383287 
>   /trunk/configure UNKNOWN 
>   /trunk/configure.ac 383287 
>   /trunk/include/asterisk/autoconfig.h.in 383287 
>   /trunk/include/asterisk/channel.h 383287 
>   /trunk/include/asterisk/manager.h 383287 
>   /trunk/main/channel.c 383287 
>   /trunk/main/json.c PRE-CREATION 
>   /trunk/main/manager.c 383287 
>   /trunk/main/manager_channels.c PRE-CREATION 
>   /trunk/main/pbx.c 383287 
>   /trunk/pbx/pbx_realtime.c 383287 
>   /trunk/res/res_json.c 383287 
>   /trunk/res/res_json.exports.in 383287 
>   /trunk/tests/test_json.c 383287 
> 
> Diff: https://reviewboard.asterisk.org/r/2381/diff
> 
> 
> Testing
> -------
> 
> Ran bouncing testsuite tests 10 times without failure.
> 
> 
> Thanks,
> 
> David
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130318/9798b4f9/attachment.htm>