<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Media Fragment URI Specification in Last Call WD</title>
	<atom:link href="http://blog.gingertech.net/2010/07/10/media-fragment-uri-specification-in-last-call-wd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gingertech.net/2010/07/10/media-fragment-uri-specification-in-last-call-wd/</link>
	<description>Silvia&#039;s blog</description>
	<lastBuildDate>Fri, 03 Feb 2012 22:04:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: silvia</title>
		<link>http://blog.gingertech.net/2010/07/10/media-fragment-uri-specification-in-last-call-wd/comment-page-1/#comment-6391</link>
		<dc:creator>silvia</dc:creator>
		<pubDate>Tue, 13 Jul 2010 11:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gingertech.net/?p=1020#comment-6391</guid>
		<description>Ben, you are right. I didn&#039;t want to go into all detail with the description, but indeed: URI fragments (&#039;#&#039;) are not ever sent to the server - instead, the MF WG has decided to transfer the information of the URI fragment in HTTP headers.</description>
		<content:encoded><![CDATA[<p>Ben, you are right. I didn&#8217;t want to go into all detail with the description, but indeed: URI fragments (&#8216;#&#8217;) are not ever sent to the server &#8211; instead, the MF WG has decided to transfer the information of the URI fragment in HTTP headers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://blog.gingertech.net/2010/07/10/media-fragment-uri-specification-in-last-call-wd/comment-page-1/#comment-6390</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 13 Jul 2010 10:56:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gingertech.net/?p=1020#comment-6390</guid>
		<description>&quot;Then, the server, upon receiving a request such as video.ogv#track=video  can redirect that to video.ogv?track=video and actually serve a new resource that satisfies the needs.  This is in fact exactly what was implemented in a recently published Firefox Plugin written by Jakub Sendor&quot;

This text is slightly confusing.  The &quot;#track=video&quot; fragment string is stripped by the browser, and never received by the server.  The Firefox plugin gets the information to the server by adding a track specifier header in the GET request, as required by the Media Fragments spec.</description>
		<content:encoded><![CDATA[<p>&#8220;Then, the server, upon receiving a request such as video.ogv#track=video  can redirect that to video.ogv?track=video and actually serve a new resource that satisfies the needs.  This is in fact exactly what was implemented in a recently published Firefox Plugin written by Jakub Sendor&#8221;</p>
<p>This text is slightly confusing.  The &#8220;#track=video&#8221; fragment string is stripped by the browser, and never received by the server.  The Firefox plugin gets the information to the server by adding a track specifier header in the GET request, as required by the Media Fragments spec.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

