|
Home > Archive > Macromedia Flash Server > March 2006 > Peldi's FLVPlayer and MM's FLVPlayback protocol/port
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Peldi's FLVPlayer and MM's FLVPlayback protocol/port
|
|
| David Bellerive 2006-03-16, 8:45 pm |
| Peldi's FLVPlayer and Macromedia's new FLVPlayback
component (which is obviously based on Peldi's
FLVPlayer) both use the same technique while
attempting to connect to FCS. They both initiate 4
different connections at an interval of 1.5 seconds
between each and uses whichever succeeds first.
Peldi's FLVPlayer uses rtmp:1935, rtmp:443, rtmp:80
and rtmps:443 in that order.
However, Macromedia's FLVPlayback component uses
rtmp:1935, rtmp:443, rtmpt:80, rtmps:443.
1) Why was the 3rd connection changed to use http
tunneling over port 80 instead of rtmp on port 80?
2) I would like to understand the logic behind this
sequence. Why is port 1935 more likely to succeed than
port 443? Why is port 443 more likely to succeed than
port 80? Why is tunneling over port 80 more likely to
succeed than secure tunneling over port 443? Why no
attempt using regular rtmp over port 80? Help me
understand this protocol/port deal please!
Dave
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around=20
http://mail.yahoo.com=20
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| James Wrubel 2006-03-16, 8:45 pm |
| I speculate that the balance might be one of performance vs. compatibility with firewalls and network protocols. I know that rtmp is generally faster than rtmpt or rtmps, however it is becoming more and more common to see firewalls that do stateful inspec
tion, meaning they not only reject outbound traffic on ports other than 80 and 443, they deny traffic on those ports that does not behave like http. My sense is, if there's any logic to the switch, it is because network configurations fall in to one of tw
o categories; either they allow everything outbound, or they only allow http outbound over 80 (and https over 443). So you should see overall faster response times with the sequence rtmp:1935, rtmp:443, rtmpt:80, rtmps:443, since users behind SPI firewall
s will connect at step 3 (or possibly step 2) rather than step 4.
David Bellerive wrote:
> Peldi's FLVPlayer and Macromedia's new FLVPlayback
> component (which is obviously based on Peldi's
> FLVPlayer) both use the same technique while
> attempting to connect to FCS. They both initiate 4
> different connections at an interval of 1.5 seconds
> between each and uses whichever succeeds first.
>
> Peldi's FLVPlayer uses rtmp:1935, rtmp:443, rtmp:80
> and rtmps:443 in that order.
>
> However, Macromedia's FLVPlayback component uses
> rtmp:1935, rtmp:443, rtmpt:80, rtmps:443.
>
> 1) Why was the 3rd connection changed to use http
> tunneling over port 80 instead of rtmp on port 80?
>
> 2) I would like to understand the logic behind this
> sequence. Why is port 1935 more likely to succeed than
> port 443? Why is port 443 more likely to succeed than
> port 80? Why is tunneling over port 80 more likely to
> succeed than secure tunneling over port 443? Why no
> attempt using regular rtmp over port 80? Help me
> understand this protocol/port deal please!
>
> Dave
>
> ________________________________________
__________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
|
|
|
|
|