- From: Arun Ranganathan <arunranga@aol.com>
- Date: Mon, 26 Feb 2007 17:58:16 -0500
- To: public-webapi@w3.org, Web APIs WG <member-webapi@w3.org>, segalerez@gmail.com
- CC: arun@arunranga.com
Erez, public-webapi, et al., I'm responsible for cleaning up the FileUpload spec.[1] which has been lying around dormant for some time. Erez, I saw email from you dated Feb 12 [2] asking about this very type of specification. Sounds like what you want is a hook to determine what to do with files chosen by <input type = "file" /> The existing work[1] provides a framework for a bit more than that. Open questions that I'd like to see discussion on the listserv to help me think about this and take this to a better place (!) are: 1. Interfaces suggested are File, FileList, FilesSelectionEvent, and FileDialog, with the exception that could thrown being FileException. I can see the FilesSelectionEvent satisfying Erez's ask for some sort of event trigger following <input type="file"/> (which could set off instantiation of FileDialog or anything else). But in general, is this overkill, underkill, just right? Should the situations that spawn FileDialog be extremely limited? Is there *really* merit in being able to get* the file as a Base64 blob in script (one of File's methods)? 2. Security. Assuming we don't chuck out some of the above interfaces, what should we do for security robustness on some of these? Suggestions welcome. I guess the ask is: what is the safest and most practical thing that can be done to meet the ask from the developer community? Your responses will help get me working on a strawperson proposal :) -- A* [1] http://dev.w3.org/cvsweb/~checkout~/2006/webapi/FileUpload/publish/FileUpload.html [2] http://lists.w3.org/Archives/Public/public-webapi/2007Feb/0058 -- Arun Ranganathan, System Architect AOL LLC http://www.arunranga.com/
Received on Monday, 26 February 2007 22:58:55 UTC