Databases
StackOverflow2013
Postsdbo
POASP.Net: Writing chunks of file..HTTP File upload with resume
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.Net: Writing chunks of file..HTTP File upload with resume
    text
    copied!<p>Please refer to question: <a href="https://stackoverflow.com/questions/2062852/resume-in-upload-file-control">Resume in upload file control</a></p> <p>Now to find a solution for the above question, I want to work on it and develop a user control which can resume a HTTP File Upload process.</p> <p>For this, I'm going to create a temporary file on server until the upload is complete. Once the uploading is done completely then will just save it to the desired location.</p> <p>The procedure I have thought of is:</p> <ol> <li>Create a temporary file with a unique name (may be GUID) on the server. </li> <li>Read a chunk of file and append it to this temp file on the server.</li> <li>Continue step 1 to 3 until EOF is reached.</li> <li>Now if the connection is lost or user clicks on <code>pause</code> button, the writing of file is stopped and the temporary file is not deleted. </li> <li>Clicking on resume again or uploading the same file again will check on the server if the file exists and user whether to <code>resume</code> or to <code>overwrite</code>. (<strong>Not sure how to check if it's the same file. Also, how to step sending the chunks from client to server.</strong>)</li> <li>Clicking on <code>resume</code> will start from where it is required to be uploaded and will append that to the file on the server. (<strong>Again not sure how to do this.</strong>)</li> </ol> <p><strong>Questions:</strong></p> <ol> <li>Are these steps correct to achieve the goal? Or need some modifications?</li> <li>I'm not sure how to implement all these steps. :-( Need ideas, links...</li> </ol> <p>Any help appreciated...</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload