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.

Labels:

Comments

  1. Ron LiddleSeptember 8, 2012 at 10:56 PM

    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

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.
Post a Comment
Read more

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...
Post a Comment
Read more

Using MobX to manage application state in a React application

I have been writing applications using React and Redux for quite some time now and thought of trying other state management solutions out there. It's not that I have faced any issues with Redux; however, I wanted to explore other approaches to state management. I recently came across MobX  and thought of giving it a try. The library uses the premise of  `Observables` to tie the application state with the view layer (React). It's also an implementation of the Flux pattern wherein it uses multiple stores to save the application state; each store referring to a particular entity. Redux, on the other hand, uses a single store with top-level state variables referring to various entities.
Post a Comment
Read more