[asterisk-bugs] [Asterisk 0011502]: [patch] allow multiple skip_ms in waitstream_core()

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11502 
====================================================================== 
Reported By:                dovidz
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11502
Category:                   Core/NewFeature
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             2007-12-10 10:29 CST
Last Modified:              2008-11-19 16:52 CST
====================================================================== 
Summary:                    [patch] allow multiple skip_ms in waitstream_core()
Description: 
this patch allows multiple skip_ms capabilities in streaming files, for
example 1 button can allow REW 500 MS, while another button would REW 5
seconds etc.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0008213 [patch] extend ControlPlayback to fwd/r...
====================================================================== 

---------------------------------------------------------------------- 
 (0095130) qwell (administrator) - 2008-11-19 16:52
 http://bugs.digium.com/view.php?id=11502#c95130 
---------------------------------------------------------------------- 
We close it.

I can't really think of any uses of it that wouldn't be better done inside
the application itself.  The API change, the duplication, and the way it's
done makes me very uneasy as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 16:52 qwell          Note Added: 0095130                          
2008-11-19 16:52 qwell          Status                   confirmed => resolved
2008-11-19 16:52 qwell          Resolution               open => suspended   
2008-11-19 16:52 qwell          Assigned To               => qwell           
======================================================================