Bug ID: JDK-4791256 SPEC: description of STOP event is inaccurate

Type: Bug
Component: client-libs
Sub-Component: javax.sound
Affected Version: 1.4.2

Priority: P4
Status: Closed
Resolution: Future Project
OS: generic
CPU: generic

Submitted: 2002-12-10
Updated: 2005-05-30
Resolved: 2005-01-22


Name: dkR10031			Date: 12/10/2002



The J2SE 1.4 API specification reads:
"
Class LineEvent.Type

public static final LineEvent.Type STOP

A type of event that is sent when a line ceases active input or output of 
audio data in response to a stop request, or because the end of media has 
been reached."

But the specification also reads about one more reason for STOP 
event generation:
"Interface SourceDataLine
......
If the delivery of audio output stops due to underflow, a STOP event is 
generated." 

If this is not the same as "end of media" then this reason should be
added to the STOP description. The description of STOP event should 
describe all cases when STOP event is generated. 

======================================================================

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon

08-07-2004

EVALUATION ###@###.### 2002-12-10 I do not like overloading the meaning of the STOP event with buffer underrun notification. So my proposal for fixing this issue is to remove the clause from the spec of SourceDataLine. For tiger, we should add an event "BFFER_XRUN" or so. Removing the clause should not create incompatibility with existing programs: even if they interpret a STOP event in between start() and stop() calls as buffer underrun, they will never receive it with this fix. AFAIK the Java Sound implementation never sends a STOP event in response to a buffer underrun/overflow.

08-07-2004

PUBLIC COMMENTS description of STOP event is inaccurate

08-07-2004

Relates :	JDK-6745051 - SourceDataLine underrun does not generate documented events or state.
Relates :	JDK-4790551 - SPEC: description of STOP event is incomplete