Re: cvs: php4 /ext/standard basic_functions.c file.c file.h /main SAPI.c
| From: | Rasmus Lerdorf | Date: | Fri, 08 Sep 2000 22:50:03 +0000 |
| Subject: | Re: cvs: php4 /ext/standard basic_functions.c file.c file.h /main SAPI.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-1648@lists.php.net to get a copy of this message | ||
> > Let's have a copy_uploaded_file() as well in case people want multiple
> > copies of this thing.
>
> Do we really need that? In the general case people would want to put the
> uploaded file in some place. Copying it around multiple times to several
> different places is no longer the general case, they can use copy() if
> they wish...
Well, I am more thinking about keeping things as backward compatible as
possible. One script in particular I remember reading through did a
copy() and then opened the temp file to check the magic cookie in
it. They could of course check the magic cookie before doing a
move_uploaded, so I guess we can skip it.
> > And when you use move_uploaded_file() what happens when the upload
> > destructor function goes to unlink the file at the end of the request?
>
> unlink() will fail..?
Right, what I meant was, shouldn't move_uploaded tell the destructor to go
away?
-Rasmus