Ultrashock Forums - View Single Post - Resume Upload

Nutrox · 2008-06-20 #4

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.

	Nutrox 17 Creative Assets	2008-06-20 #4
	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.