On 08 Apr 2014, at 14:01, Joshua Colp <[email protected]> wrote: > Olle E. Johansson wrote: > > <snip> > >>>> >>>> 3. Invent AST_FRAME_DROP and make sure that we drop it instead >>>> of sending it out to network... >>> That's what&ast_null_frame is for. It's a globally created frame >>> which is used to replace frames with nothing or return a frame when >>> no real frame exists to return. It just passes through stuff and >>> nothing happens with it, since it contains er well nothing. Since >>> it is globally created it also doesn't incur a memory allocation in >>> most cases. >> >> Right. What you mean is that there's no way around it, just go for >> option #2 and do what Josh says again... ;-) > > I think it would be what I would do, indeed.
Do you always do what you say you should do? That may be or not be scary. /O ;-) -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
