the Session extension does. But this double
strategy would complicate the code in rfc1867.c and yield very marginal
gain.
If there's enough interest in this, I will rework the patch according to
Sara's hint.
Cheers,
David
--
David Santinoli
Tieffe Sistemi S.r.l.
urity feature". Not in the least.
Instead, my intent was to make hash computation easier and faster for
those (rather common) cases in which signatures are used for duplicate
file detection etc..
Cheers,
David
--
David Santinoli
Tieffe Sistemi S.r.l. viale Piceno 2
ield, as in the MAX_FILE_SIZE case.)
The result is found in the special variables
$_FILES[userfile]["md5"] and $_FILES[userfile]["sha1"].
These variables are only defined upon request of the corresponding
digest.
The patch was produced against the php6 CVS version of rfc1867.c
(1.190).
n attribute to the INPUT element - has some merit, but I
don't know how viable this road is (in terms of functionalities already
present in the PHP core), and I'd also like to stick to "standard" HTML.
Cheers,
David
--
David Santinoli, Milano + <[EMAIL PROTECTE
way?
Do you refer to the PHP_MD5_CTX and PHP_SHA1_CTX contexts?
AFAIK, given they're automatic variables with no malloc()ed buffers
inside them, it doesn't look like an explicit cleanup is needed.
Cheers,
David
PS I'm on the list! CC:ing to my private address is unnecess
ot;md5"] and $_FILES[userfile]["sha1"].
These variables are only defined upon request of the corresponding
digest.
The patch was produced against the current CVS version of rfc1867.c
(PHP_5_0 branch, v1.160).
Cheers,
David
--
David Santinoli, Milano + <[EMA
ile]["md5"] and $_FILES[userfile]["sha1"].
These variables are only defined upon request of the corresponding
digest.
The patch was produced against the current CVS version of rfc1867.c
(PHP_4_3 branch, v1.122.2.14).
Cheers,
David
--
David Santinoli, Milano + <
CVS file (v1.141) as well.
Cheers,
David
--
David Santinoli, Milano + <[EMAIL PROTECTED]>
Independent Linux/Unix consultant + http://www.santinoli.com
--- rfc1867.c.cvs 2003-06-25 16:54:28.0 +0200
+++ rfc1867.c 2003-06-25 16:58:40.0 +0200
@@ -32,6 +32