id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,thread
951,RTMPT fallback,pablo,jeroen,"From Martin:

{{{
It seems to take JWPlayer to take over minute to recognize that RTMP doesn't work 
and to then try RTMPT. My workaround is to specify RTMPT in the playlist, but now
bitrate switching stutters.

I think that the reason for this is that JWPlayer is implementing Adobe's old standard 
procedure of sequentially trying out RTMP over various ports before trying RTMPT (as 
described in http://kb2.adobe.com/cps/166/tn_16631.html ).

Other players implement a parallel approach, wherein an RTMP and an RTMPT 
connections are opened at the same time and whichever connects first is used (as 
described at the bottom of http://kb2.adobe.com/cps/185/tn_18537.html : ""To 
alleviate this delay, the SimpleConnect component has been improved to make two 
connection attempts, 250 milliseconds apart: the first uses RTMP and the second uses 
RTMPT. When one connection succeeds, the other is discarded. This dramatically 
decreases the time it takes for a connection to be established."")

}}}

We should implement the simultaneous connection approach, and use whichever connection returns first.

|| Streamer || Behavior ||
|| rtmp:// || Connect to both RTMP and RTMPT, use whichever responds first ||
|| rtmpt:// || Only connect to RTMPT ||
|| rtmpe:// || Connect to both RTMPE and RTMPTE, use whichever responds first ||
|| rtmpte:// || Only connect to RTMPTE ||",feature,closed,,Player 5.4,embedding,fixed,,pablo,