<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Programmer's testimony &#187; RTMP</title>
	<atom:link href="http://en.jakubiak.info/tag/rtmp/feed" rel="self" type="application/rss+xml" />
	<link>http://en.jakubiak.info</link>
	<description>My experience with: Java, JEE, Adobe Flex, PHP, Video</description>
	<lastBuildDate>Wed, 25 Nov 2009 19:02:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>RTMP – how it make YouTube?</title>
		<link>http://en.jakubiak.info/2009/10/07/rtmp-%e2%80%93-how-it-make-youtube.html</link>
		<comments>http://en.jakubiak.info/2009/10/07/rtmp-%e2%80%93-how-it-make-youtube.html#comments</comments>
		<pubDate>Wed, 07 Oct 2009 16:19:02 +0000</pubDate>
		<dc:creator>Antoni Jakubiak</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Red5]]></category>
		<category><![CDATA[RTMP]]></category>

		<guid isPermaLink="false">http://en.jakubiak.info/2009/10/07/rtmp-%e2%80%93-how-it-made-youtube.html</guid>
		<description><![CDATA[There is a problem with RTMP. It works on 1935 port. In fact it&#8217;s not a problem with RTMP but with ISP. ISP like filtering internet traffic and like packets queuing. That&#8217;s why connections on port 1935 – which is not wheel – known in Internet – work worse than connection on port 80. Adobe [...]]]></description>
			<content:encoded><![CDATA[<p>There is a problem with <span style="color:#9bbb59">RTMP</span>. It works on 1935 port. In fact it&#8217;s not a problem with <span style="color:#9bbb59">RTMP</span> but with ISP. ISP like filtering internet traffic and like packets queuing. That&#8217;s why connections on port 1935 – which is not wheel – known  in Internet – work worse than connection on port 80. Adobe know that and have introduced <span style="color:#c0504d">RTMPT</span>, which is an encapsulation of <span style="color:#9bbb59">RTMP</span> in HTTP, which works on port 80. 
</p><p>YouTube does something else. You see, You Tube allows recording from web cam. It uses <span style="color:#9bbb59">RTMP</span> to do that, but <span style="color:#9bbb59">RTMP</span> works on HTTP (80) port. I noticed it by using <a href="http://www.netlimiter.com/" onclick="pageTracker._trackPageview('/outgoing/www.netlimiter.com/?referer=');">NetLimiter</a>. 
</p><p><img src="http://en.jakubiak.info/wp-content/uploads/2009/10/100709_1618_RTMPhowitm1.png" alt=""/>
	</p><p>I decided to check it carefully.  Is it <span style="color:#9bbb59">RTMP</span> on its unusual port or is it usual <span style="color:#c0504d">RTMPT</span>? Using <a href="http://www.wireshark.org/" onclick="pageTracker._trackPageview('/outgoing/www.wireshark.org/?referer=');">Wireshark</a> as my oxygen supply, I dove deep in the hidden depths of the system. Wireshark allows me to sniff internet traffic. I was wondering what exactly my laptop send to YouTube. I would have expected many POST requests for <span style="color:#c0504d">RTMPT</span>. There weren&#8217;t. It was something like
</p><p><img src="http://en.jakubiak.info/wp-content/uploads/2009/10/100709_1618_RTMPhowitm2.png" alt=""/>
	</p><p>instead. <em>rtmp:/…webcam.youtube:80/</em> &#8211; 99% YouTube use <span style="color:#9bbb59">RTMP</span> on port 80. 
</p><p>It&#8217;s an interesting idea. I can check it out to give me an idea of how to write similar routines.  
</p><p>
 </p>]]></content:encoded>
			<wfw:commentRss>http://en.jakubiak.info/2009/10/07/rtmp-%e2%80%93-how-it-make-youtube.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
