<?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: Large file uploads over HTTP - the final solution (I think)</title>
	<atom:link href="http://michaelshadle.com/2008/08/26/large-file-uploads-over-http-the-final-solution-i-think/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelshadle.com/2008/08/26/large-file-uploads-over-http-the-final-solution-i-think/</link>
	<description>"Sometimes I don't know why I even fucking try"</description>
	<lastBuildDate>Fri, 12 Mar 2010 09:12:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mike</title>
		<link>http://michaelshadle.com/2008/08/26/large-file-uploads-over-http-the-final-solution-i-think/comment-page-1/#comment-9817</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Fri, 12 Dec 2008 19:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=87#comment-9817</guid>
		<description>Yes, see: http://michaelshadle.com/2008/12/03/updates-on-the-http-file-upload-front-part-2/

I&#039;ll be sharing some code when I have some time to clean it up and isolate it properly.</description>
		<content:encoded><![CDATA[<p>Yes, see: <a href="http://michaelshadle.com/2008/12/03/updates-on-the-http-file-upload-front-part-2/" rel="nofollow">http://michaelshadle.com/2008/12/03/updates-on-the-http-file.....nt-part-2/</a></p>
<p>I'll be sharing some code when I have some time to clean it up and isolate it properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronnie</title>
		<link>http://michaelshadle.com/2008/08/26/large-file-uploads-over-http-the-final-solution-i-think/comment-page-1/#comment-9811</link>
		<dc:creator>Ronnie</dc:creator>
		<pubDate>Fri, 12 Dec 2008 17:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=87#comment-9811</guid>
		<description>Sounds interesting.
Any news on it?
Cheers</description>
		<content:encoded><![CDATA[<p>Sounds interesting.<br />
Any news on it?<br />
Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://michaelshadle.com/2008/08/26/large-file-uploads-over-http-the-final-solution-i-think/comment-page-1/#comment-6447</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 27 Aug 2008 15:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=87#comment-6447</guid>
		<description>In laymen&#039;s terms I tried to make it into a conversation, and I think I determined that I could send even less information back and forth.

Client says: &quot;I have $filename and want to upload it&quot; (action = &#039;begin&#039;)
Server says: &quot;I am ready, here is your $transaction_id&quot; (status = &#039;OK&#039;, transaction = &#039;transaction id&#039;)

Client says: &quot;Here is segment $segment_id for transaction $transaction_id it has $size bytes and md5 checksum is $checksum, and the body is uuencode($body)&quot; (action = &#039;process&#039;)
Server says: &quot;I have received $segment_id for transaction $transaction_id&quot; (repeat these two as many times as needed) - the server is reporting success or not based on (status = &#039;OK&#039;, transaction = &#039;transaction id&#039;)

Client says: &quot;I&#039;m all done with $transaction_id now. Final full file checksum is $checksum and $size bytes&quot; (action = &#039;finish&#039;)
Server says: &quot;I have received $transaction_id in full&quot; (status = &#039;OK&#039;, transaction = &#039;transaction id&#039;)

Client now knows the server has received the file in full and moves on to the next file (if uploading multiple files)

This is starting to feel more and more like parts of a Usenet client reused to work with HTTP :)</description>
		<content:encoded><![CDATA[<p>In laymen's terms I tried to make it into a conversation, and I think I determined that I could send even less information back and forth.</p>
<p>Client says: "I have $filename and want to upload it" (action = 'begin')<br />
Server says: "I am ready, here is your $transaction_id" (status = 'OK', transaction = 'transaction id')</p>
<p>Client says: "Here is segment $segment_id for transaction $transaction_id it has $size bytes and md5 checksum is $checksum, and the body is uuencode($body)" (action = 'process')<br />
Server says: "I have received $segment_id for transaction $transaction_id" (repeat these two as many times as needed) - the server is reporting success or not based on (status = 'OK', transaction = 'transaction id')</p>
<p>Client says: "I'm all done with $transaction_id now. Final full file checksum is $checksum and $size bytes" (action = 'finish')<br />
Server says: "I have received $transaction_id in full" (status = 'OK', transaction = 'transaction id')</p>
<p>Client now knows the server has received the file in full and moves on to the next file (if uploading multiple files)</p>
<p>This is starting to feel more and more like parts of a Usenet client reused to work with HTTP <img src='http://michaelshadle.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
