This looks good except for one thing. I know the SDP spec says that all 
SDP lines will end with a '\r\n', but in practice that is not always the 
case. Even RealNetworks is guilty of violating this in the past. You 
should change the code so that it also handles cases where the line is 
terminated with only '\r' or '\n'.

Aaron

On Mon, 1 Dec 2003, Damon Lanphear wrote:

> Description:
> 
> Some encoders provide an additional stream header field: SDPData, which
> is SDP formatted header information that is placed inline into the
> generated SDP file.
> 
> These encoders may also include a b=AS line that conflicts with existing
> b=AS lines written in all outbound SDP files.
> 
> This conflicting b=AS line causes unpredictable behavior in RTSP/RTP
> clients.
> 
> Solution:
> 
> If b=AS lines are present in the SDPData field, remove the extraneous
> b=AS line.
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at protocol.helixcommunity.org
For additional commands, e-mail: dev-help at protocol.helixcommunity.org