<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>InfoSauce: Multiple file upload and the abuse of buzzwords</title>
  <id>tag:blog.infosauce.com,2005:Typo</id>
  <generator uri="http://www.typosphere.org" version="4.0">Typo</generator>
  <link href="http://blog.infosauce.com/xml/atom/article/2/feed.xml" rel="self" type="application/atom+xml"/>
  <link href="http://blog.infosauce.com/articles/2005/09/28/multiple-file-upload-and-the-abuse-of-buzzwords" rel="alternate" type="text/html"/>
  <updated>2006-10-26T21:43:31-07:00</updated>
  <entry>
    <author>
      <name>Tim</name>
    </author>
    <id>urn:uuid:3e9bd75b-7c18-438a-8296-eabbab69edf9</id>
    <published>2005-09-28T06:59:00-07:00</published>
    <updated>2006-10-26T21:43:31-07:00</updated>
    <title type="html">Multiple file upload and the abuse of buzzwords</title>
    <link href="http://blog.infosauce.com/articles/2005/09/28/multiple-file-upload-and-the-abuse-of-buzzwords" rel="alternate" type="text/html"/>
    <category term="general" scheme="http://blog.infosauce.com/articles/category/general" label="General"/>
    <category term="css-dom-standards" scheme="http://blog.infosauce.com/articles/category/css-dom-standards" label="CSS-DOM-standards"/>
    <summary type="html">&lt;p&gt;&lt;a href="http://the-stickman.com/"&gt;Stickman&lt;/a&gt; has posted a &lt;a href="http://the-stickman.com/web-development/javascript/upload-multiple-files-with-a-single-file-element/"&gt;cool &lt;span class="caps"&gt;DOM&lt;/span&gt;-scripted multiple form upload&lt;/a&gt; and, of course, through no fault of his, commentors are assumming it must be &lt;span class="caps"&gt;AJAX&lt;/span&gt;, since it&amp;#8217;s on the web and it&amp;#8217;s new and cool.  &lt;a href="http://www.quirksmode.org/blog/archives/2005/06/you_shouldve_be_1.html"&gt;PPK has talked about this issue before&lt;/a&gt; but it looks like calling everything &amp;#8220;AJAX&amp;#8221; really is spreading to even geek bloggers watching web development (it&amp;#8217;s only in the talkbacks, so far) who you would hope would be Marketing-ese proof.&lt;/p&gt;


	&lt;p&gt;Now, we&amp;#8217;ve got nothing against &lt;span class="caps"&gt;AJAX&lt;/span&gt;, it&amp;#8217;s a great technique that we like using, as appropriate, but this is &lt;span class="caps"&gt;DOM&lt;/span&gt;-scripting pure and simple.  &lt;span class="caps"&gt;AJAX&lt;/span&gt;-like technologies have to do with how you handle the round trip to the server without reloading the page and, in this context, would look more like &lt;a href="http://ktk.xs4all.nl/stuff/html/simultaneous-uploading-using-iframes/"&gt;this&lt;/a&gt;  (thanks to one of the other posters for the link). &lt;span class="caps"&gt;AJAX&lt;/span&gt; could be added onto Stickman&amp;#8217;s work to just refresh the part of the page handling the upload, and something similar is used by Basecamp, already, to get around the multiple file upload another way.&lt;/p&gt;


	&lt;p&gt;Personally, I think what Stickman is doing is far cooler than &lt;span class="caps"&gt;AJAX&lt;/span&gt;, as he&amp;#8217;s getting around a more fundamental browser limitation.  What you can do with the &lt;span class="caps"&gt;HTML&lt;/span&gt; form upload control is severely restricted in browsers, largely for security reasons.  For too long  it&amp;#8217;s been a basic assumption in web development that you might as well not try to do anything fancy with the form upload widget, since it&amp;#8217;s fairly locked down.  In fact, it&amp;#8217;s still possible for the browser implementors to decide that hiding the widget is a potential security risk, and then this technique goes out the window.  Until then, though, it&amp;#8217;s useful to have in the toolbox, and even if it gets locked-out by some browsers in the future, it still gets us thinking about how to work around those limitations again.&lt;/p&gt;


	&lt;p&gt;Generally, I think the Basecamp approach of actually doing it through &lt;span class="caps"&gt;AJAX &lt;/span&gt;(similar to the &amp;#8220;this&amp;#8221; link above) would often be a better choice, as it allows more granular feedback and control.  For instance they confirm each upload and then allow you to re-label it prior to sending a message off.  This also avoids having to wait for one massive upload at the end, which might kill your whole message, instead of just the individual upload. Regardless, Stickman&amp;#8217;s approach is still cool.&lt;/p&gt;
</summary>
    <content type="html">&lt;p&gt;&lt;a href="http://the-stickman.com/"&gt;Stickman&lt;/a&gt; has posted a &lt;a href="http://the-stickman.com/web-development/javascript/upload-multiple-files-with-a-single-file-element/"&gt;cool &lt;span class="caps"&gt;DOM&lt;/span&gt;-scripted multiple form upload&lt;/a&gt; and, of course, through no fault of his, commentors are assumming it must be &lt;span class="caps"&gt;AJAX&lt;/span&gt;, since it&amp;#8217;s on the web and it&amp;#8217;s new and cool.  &lt;a href="http://www.quirksmode.org/blog/archives/2005/06/you_shouldve_be_1.html"&gt;PPK has talked about this issue before&lt;/a&gt; but it looks like calling everything &amp;#8220;AJAX&amp;#8221; really is spreading to even geek bloggers watching web development (it&amp;#8217;s only in the talkbacks, so far) who you would hope would be Marketing-ese proof.&lt;/p&gt;


	&lt;p&gt;Now, we&amp;#8217;ve got nothing against &lt;span class="caps"&gt;AJAX&lt;/span&gt;, it&amp;#8217;s a great technique that we like using, as appropriate, but this is &lt;span class="caps"&gt;DOM&lt;/span&gt;-scripting pure and simple.  &lt;span class="caps"&gt;AJAX&lt;/span&gt;-like technologies have to do with how you handle the round trip to the server without reloading the page and, in this context, would look more like &lt;a href="http://ktk.xs4all.nl/stuff/html/simultaneous-uploading-using-iframes/"&gt;this&lt;/a&gt;  (thanks to one of the other posters for the link). &lt;span class="caps"&gt;AJAX&lt;/span&gt; could be added onto Stickman&amp;#8217;s work to just refresh the part of the page handling the upload, and something similar is used by Basecamp, already, to get around the multiple file upload another way.&lt;/p&gt;


	&lt;p&gt;Personally, I think what Stickman is doing is far cooler than &lt;span class="caps"&gt;AJAX&lt;/span&gt;, as he&amp;#8217;s getting around a more fundamental browser limitation.  What you can do with the &lt;span class="caps"&gt;HTML&lt;/span&gt; form upload control is severely restricted in browsers, largely for security reasons.  For too long  it&amp;#8217;s been a basic assumption in web development that you might as well not try to do anything fancy with the form upload widget, since it&amp;#8217;s fairly locked down.  In fact, it&amp;#8217;s still possible for the browser implementors to decide that hiding the widget is a potential security risk, and then this technique goes out the window.  Until then, though, it&amp;#8217;s useful to have in the toolbox, and even if it gets locked-out by some browsers in the future, it still gets us thinking about how to work around those limitations again.&lt;/p&gt;


	&lt;p&gt;Generally, I think the Basecamp approach of actually doing it through &lt;span class="caps"&gt;AJAX &lt;/span&gt;(similar to the &amp;#8220;this&amp;#8221; link above) would often be a better choice, as it allows more granular feedback and control.  For instance they confirm each upload and then allow you to re-label it prior to sending a message off.  This also avoids having to wait for one massive upload at the end, which might kill your whole message, instead of just the individual upload. Regardless, Stickman&amp;#8217;s approach is still cool.&lt;/p&gt;

</content>
  </entry>
  <entry>
    <author>
      <name>Tim Connor</name>
    </author>
    <id>urn:uuid:887b9e23-ee7b-402b-adfa-b73580420b2a</id>
    <published>2005-11-25T08:34:56-08:00</published>
    <updated>2006-10-22T21:34:46-07:00</updated>
    <title type="html">Comment on Multiple file upload and the abuse of buzzwords by Tim Connor</title>
    <link href="http://blog.infosauce.com/articles/2005/09/28/multiple-file-upload-and-the-abuse-of-buzzwords#comment-5" rel="alternate" type="text/html"/>
    <content type="html">&lt;p&gt;You’re right, but it’s a hell of a lot closer, in that it at least does an asychronous server call. To really be AJAX, yes you’d have to use Javascript and the XHR object. I wouldn’t pick nits, though, over the use of iframes, if you were doing that dynamically. It’s doing non-reloading interface stuff, based on asynchronous calls to the server that is what AJAX is really about, to me.&lt;/p&gt;</content>
  </entry>
  <entry>
    <author>
      <name>Krijn Hoetmer</name>
    </author>
    <id>urn:uuid:45eaba57-0b32-44ec-b088-d47f71a3d679</id>
    <published>2005-11-25T08:34:54-08:00</published>
    <updated>2006-10-22T21:34:46-07:00</updated>
    <title type="html">Comment on Multiple file upload and the abuse of buzzwords by Krijn Hoetmer</title>
    <link href="http://blog.infosauce.com/articles/2005/09/28/multiple-file-upload-and-the-abuse-of-buzzwords#comment-4" rel="alternate" type="text/html"/>
    <content type="html">&lt;p&gt;Just a note; my &lt;a href="http://krijnhoetmer.nl/stuff/html/simultaneous-uploading-using-iframes/" rel="nofollow"&gt;version&lt;/a&gt; is just some simple use of HTML and should not be used as an example of ‘AJAX’ :)&lt;/p&gt;</content>
  </entry>
  <entry>
    <author>
      <name>matelot</name>
    </author>
    <id>urn:uuid:4dbd2385-3e83-404f-9098-97c0c65f5164</id>
    <published>2005-11-06T08:33:45-08:00</published>
    <updated>2006-10-22T21:34:45-07:00</updated>
    <title type="html">Comment on Multiple file upload and the abuse of buzzwords by matelot</title>
    <link href="http://blog.infosauce.com/articles/2005/09/28/multiple-file-upload-and-the-abuse-of-buzzwords#comment-3" rel="alternate" type="text/html"/>
    <content type="html">&lt;p&gt;It’s F#$%KING unbelievable how many people call that “Ajaxian” !!!&lt;/p&gt;</content>
  </entry>
</feed>
