Skip to main content

Uploading chunks of a large file using XHR2

I was having a conversation with my college friend about the enhancements in XHR2 and I was showing him how one can upload a file to the server using plain Ajax. He asked me whether I can upload a large file to the server such as a video file. I tried doing that but was bumped when the server reported with 400 error telling me that the 'POST size has exceeded maximum limit'. This got me thinking whether I can upload chunks of a large file to the server. I referred to the FileSystem API and came across the slice method that allows you to get a fragment of a file.

The slice method takes two parameters which specifies the start and end byte position of the fragment that is to be extracted. This fragment can then be uploaded to the server using XHR2.

Here’s the client code:

Here I’ve specified the chunk size as 1 MB (1024*1024) and then slicing the file such that each fragment is of 1 MB in size. Each of this fragments is then pushed to an array and then uploaded to the server using XHR2. Each fragment is a ByteArray and is sent to server synchronously.

Here’s the server side code:


The ByteArray is then written\appended to the file by calling the write method on the FileOutputStream object.

Output:

           Uploading chunk of size 1048576.
           Chunk of size 1048576 uploaded successfully.
           Uploading chunk of size 1048576.
           Chunk of size 1048576 uploaded successfully.
           Uploading chunk of size 1048576.
           Chunk of size 1048576 uploaded successfully.
           Uploading chunk of size 17540.
           Chunk of size 17540 uploaded successfully.

Here you can see that each fragment is of size 1 MB and the last fragment is of 17 KB. I've tried uploading large images and videos of size greater than 50 MB and it works fine.

Comments

  1. It is possible to send the file over Internet without uploading them anywhere by using a tool called Binfer. Binfer has no limitation on file size and quantity. You can send large files without any worry. Visit http://www.binfer.com for details

    ReplyDelete

Post a Comment

Popular posts from this blog

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o