in reply to Browser-based file uploads and deletions for a

How astute is the common use of this application. No matter what you can copy the file while processing. If this is a common user I think you can just use a browser base upload but don't use the upload terminology. Something along the lines of saying process (not upload) and never actually storing the file on your machine (or you do and just never let them know. If you did use a non-browser upload how will the processing be triggered? Just an ide.s ---- I always wanted to be somebody... I guess I should have been more specific.
  • Comment on Re: Browser-based file uploads and deletions for a

Replies are listed 'Best First'.
Re: Re: Browser-based file uploads and deletions for a
by Hero Zzyzzx (Curate) on Nov 18, 2001 at 08:28 UTC

    I think you're right, atlantageek. This is really a question of social engineering and trust. If you call it "convert" or "process", rather than "upload" I bet 99% of folks wouldn't have an issue with it.

    If it were me, I'd just write it so that the subroutines I use to do the conversion unlink() the files right after processing. Maybe you could write a sub that opens and prints the document (with the correct mime-type, of course) to tbe browser, and as its last action it unlinks the file. (Don't forget binmode if you're on windows) As long as the user doesn't press "stop" and the download of the converted document completes, you should have no record of the file being there, and it's essentially a download once system.

    -Any sufficiently advanced technology is
    indistinguishable from doubletalk.