Fluid Uploader Component
What problem are we solving?
Currently most web applications use the standard
http file browse and upload service provided with the
<input type="file"> form field.
- Only one file can be selected at a time for upload.
- Interface is inconsistent from browser to browser even down to the labels on the browse button.
- The application can not specify the file type or types that are accepted in the current context.
- The browser does not provide meaningful or consistent feedback on the upload process.
A number of web applications get around the standard browse and upload experience by using Flash or Java in the browser, or creating stand-alone desktop interfaces to handle file uploading. Some of these solutions work very well but do not feel integrated with the application context, and they are difficult for the developers to modify or integrate with their applications.
How are we meeting the needs?
The Fluid Uploader uses an approach to browser-based file uploading used by Flickr and the YUI library. This technique uses a small Flash object, with no user-interface of its own, to call a standard OS file open dialog that allows the user to select multiple files, and then uses the same Flash object to manage the interaction with the server to provide good progress feedback to the user during the file upload.
[The Flash file upload library that we're using for the Fluid Uploader is the SWFupload library. http://www.swfupload.org From this library our component uses the Flash component and swfupload.js file which handles the communication between the swf and the UI.]
Roadmap, Known issues, and Task List
- Application developers and system integrators must be careful to manage security. (We'll fill-in more about this later.)
- Because a standard OS file open dialog is called, any application specific feedback for the user can only be given to the user before or after file browsing.
- Error Handling is nonexistent at this time.