Flash
ActionScript

Author
2189

0

4
Resume Upload - possible?

Last reply Jun 24 2008, 02:15 PM

by wraevn

Posted: Jun 20 2008, 04:23 PM

by wraevn

So you’ve got somebody uploading a bunch of huge files (FileReferenceList) in your Flash or Flex app (NOT AIR).

Something happens - they lose power, connectivity, they accidentally log off etc.

They log in again, get reconnected etc. ...

Is it possible to:

a) automatically locate those orphaned uploads w/out them having to browse and select them again (basically, storing the FileReferenceList - in an FSO maybe?) so you can automatically start uploading them again?

b) find out where the upload of each file got cut off and resume the upload from there (instead of having to upload the whole bloody thing from scratch)

Thanks!

4 REPLIES

Nutrox

Resuming the file upload from where it was cut off isn’t possible because you can’t access the file system directly from the Flash Player. It is possible with AIR though as long as you keep track of where the data is being stored on the server… but I guess that isn’t of much use to you for this.

The first question is an interesting one though. I don’t think that will be possible either unless a FileReferenceList object can be serialised properly. I can try a few things out for you later today if it will help.

20 June 2008 05:08 PM

Author

wraevn

If serializing a FileReference is what’s necessary - would this work?

http://www.mikechambers.com/blog/2007/06/22/serializing-file-reference-instances-in-adobe-air/

I hesitated delving too deep w/ this as it’s in reference to an AIR project, but perhaps ... ?

20 June 2008 05:18 PM

Nutrox

The File class is a bit different to FileReference because the FileReference’s name property is read-only which means you wouldn’t be able to restore the name/path of the file again when the object was restored. I don’t think the full system path to the file is public either. If the filename/path is stored as a private variable within the FileReference class then this isn’t going to be possible unfortunately. So, getting a FileReference object to serialise properly is possible but restoring the filename/path when the object is restored probably isn’t, and that puts a big spanner in the works.