[asterisk-dev] [Code Review] 2642: app_bridgewait: Add a name argument so that multiple holding bridges may be used

[jrose]

> On July 10, 2013, 12:25 a.m., rmudgett wrote:
> > /trunk/apps/app_bridgewait.c, lines 377-382
> > <https://reviewboard.asterisk.org/r/2642/diff/6/?file=41198#file41198line377>
> >
> >     Reference inconsistency.  The find returns a ref while the alloc does not return a ref.


> On July 10, 2013, 12:25 a.m., rmudgett wrote:
> > /trunk/apps/app_bridgewait.c, line 109
> > <https://reviewboard.asterisk.org/r/2642/diff/6/?file=41198#file41198line109>
> >
> >     How about to changing the name to wait_bridges?  Or if you prefer wait_wrappers.

I'll make it so. But I'm calling it wait_bridge_wrappers because I'm an excessively verbose person.


- jrose


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


On July 8, 2013, 6:12 p.m., jrose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2642/
> -----------------------------------------------------------
> 
> (Updated July 8, 2013, 6:12 p.m.)
> 
> 
> Review request for Asterisk Developers, Matt Jordan and rmudgett.
> 
> 
> Bugs: ASTERISK-21922
>     https://issues.asterisk.org/jira/browse/ASTERISK-21922
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> Previously the holding bridge used for bridgewait was a single bridge that once created would stick around until the application was unloaded.
> 
> Now things are a little more complicated. Each holding bridge has a name and will be destroyed when it is empty. Since it's theoretically possible to have channels enter a holding bridge without going through the bridge wait application, it isn't always possible to deliberately control when the bridge will be destroyed, so the bridge can effectively be abandoned and set to be destroyed once it empties out.
> 
> 
> Diffs
> -----
> 
>   /trunk/apps/app_bridgewait.c 393824 
>   /trunk/include/asterisk/bridging.h 393824 
>   /trunk/main/bridging.c 393824 
> 
> Diff: https://reviewboard.asterisk.org/r/2642/diff/
> 
> 
> Testing
> -------
> 
> Tested multiple simultaneous holding bridges, multiple channels in the same holding bridge, what would happen if one channel entered as another one was leaving but before the bridge was destroyed, tested bridges emptying out, tested module unload and module load after unload.
> 
> 
> Thanks,
> 
> jrose
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130715/33d90357/attachment-0001.htm>