SWFUpload Code

17 lines (9 with data), 2.4 kB

#labels Featured
v2.5.0 implements several new features requested by users. Most notably Client-Side image resizing.


== Details ==

v2.5.0 Beta 1 should be pretty stable.  We've fixed most of the bugs that we've been notified of since the last release.  There are still many Flash Player bugs that plague us but there is little we can do about them.

v2.5.0 Beta 2 is almost ready to release.  Beta 1 had a lot more bugs than we realized. Hopefully they are all squared away. We've got a couple outstanding issues to correct and a little more testing to do.   We also have some bug reports that we cannot confirm (especially on Linux and Mac platforms).  The more information and detail you can provide the better we'll be by release time.

== Limitations ==

  * Resized image uploads are sent as binary posts and not as files.  This does not affect the client very much but changes how data is handled by the server. We are forced to upload this way because of Flash's over protective security. If the string "filename" appears in the upload data then a security error is triggered by the Flash Player.  Unfortunately providing a file name is also what triggers the server to treat the upload as a file rather than a post. For PHP developers this means the file data appears in $`_`POST rather than $`_`FILE and your server side tech may not stream the data to disk like it does for large files.  Instead it may be stored entirely in memory. This may mean you'll need to keep your resized data small so as to not overwhelm the server or hit memory usage limits.  ASP.Net developers may want to write an HTTPModule or HTTPHandler to intercept the file data before it streamed to memory (disclaimer: we don't know if this will work or is even possible).

  * Upload Progress is not available for resized image uploads.  We rely on the Flash Player to provide those events and it only provides that data for file uploads using the FileReference API.  When uploading our own custom data we do not get these events.

  * The button image now scales properly when zoomed by the browser.  However, this means that the image sprite MUST be 4X the button height. In previous versions you could get away with images 3X the button height (leaving out the disabled state image).  This will no longer work. Unfortunately we can't figure out how to scale the text as well. It stays the same size and in the same position.