rfc:session_upload_progress
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:session_upload_progress [2008/09/08 10:08] – typo lbarnaud | rfc:session_upload_progress [2008/09/27 09:29] – error number lbarnaud | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2008-09-08 | * Date: 2008-09-08 | ||
* Author: Arnaud Le Blanc < | * Author: Arnaud Le Blanc < | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
* Patch: http:// | * Patch: http:// | ||
Line 20: | Line 20: | ||
Using the session extension for this purpose also allows to use the different storage backends available. | Using the session extension for this purpose also allows to use the different storage backends available. | ||
- | The patch comes with 4 ini settings, working just like APC's ones: | + | The patch comes with some ini settings, working just like APC's ones: |
* session.upload_progress.enabled[=1] | * session.upload_progress.enabled[=1] | ||
Line 26: | Line 26: | ||
* session.upload_progress.name[=PHP_SESSION_UPLOAD_PROGRESS] | * session.upload_progress.name[=PHP_SESSION_UPLOAD_PROGRESS] | ||
* session.upload_progress.freq[=1%] | * session.upload_progress.freq[=1%] | ||
+ | * session.upload_progress.min_freq[=0.0] | ||
When session.upload_progress.enabled is set to 1, and $_POST[session.upload_progress.name] is set and non-empty, upload informations are stored in $_SESSION[session.upload_progress.prefix . $_POST[session.upload_progress.name]]. | When session.upload_progress.enabled is set to 1, and $_POST[session.upload_progress.name] is set and non-empty, upload informations are stored in $_SESSION[session.upload_progress.prefix . $_POST[session.upload_progress.name]]. | ||
Line 31: | Line 32: | ||
$_POST[session.upload_progress.name] allows to follow multiple uploading-requests on the same session at the same time. Nothing will be done if it is not set or empty, so that session.upload_progress.enabled can be left to 1 without overhead (also, the upload hook is never called on non multipart/ | $_POST[session.upload_progress.name] allows to follow multiple uploading-requests on the same session at the same time. Nothing will be done if it is not set or empty, so that session.upload_progress.enabled can be left to 1 without overhead (also, the upload hook is never called on non multipart/ | ||
- | The session.upload_progress.freq | + | The session.upload_progress.prefix is used to avoid conflicts with existing session vars. |
+ | |||
+ | The session.upload_progress.freq | ||
The patch also allows to follow multiple files in the same request. Each file will have its own $_FILES-like array with name, tmp_name, error, bytes processed, etc. | The patch also allows to follow multiple files in the same request. Each file will have its own $_FILES-like array with name, tmp_name, error, bytes processed, etc. | ||
Line 79: | Line 82: | ||
</ | </ | ||
+ | The current patch also allows to cancel an upload by setting the " | ||
+ | |||
+ | Doing so will cancel the currently uploading file, bypass all remaining data (POST variables, uploads, etc). An upload canceled this way will have " | ||
rfc/session_upload_progress.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1