On 2005.6.4, at 04:31 AM, Ken Williams wrote:
On Jun 3, 2005, at 7:34 AM, Ken Williams wrote:
On Jun 2, 2005, at 10:16 AM, Bill Stephenson wrote:
So I guess what I'm asking is if there a way to get either of these
apps to upload a file with a new name and rename it after the upload
is complete with one click. Obviously, this doesn't entirely solve
the problem, but it does reduce the potential.
Actually, it *would* entirely solve the problem. Renaming a file is
an atomic operation, there's no point at which anybody could get a
partial file. People still reading the old file would be fine too,
even if the rename happened while they're in the middle of reading;
the old file is readable until they close it.
Peter pointed out in a private email that this isn't reliable using
FTP's rename functionality
I'd like a peek at what he wrote, if nobody minds.
(if your FTP even supports it) - what I meant in the above, though I
wasn't clear, was to use /bin/mv on the server, not a rename through
the FTP connection.
Now, I wouldn't want to stir too much oil into the water, but I'm
imagining strange things like, ssh would not have such problems
(assuming you knew that the server was a regular *NIX server and the
server's file system was a system with proper inodes)?
I consider this on topic, myself, because it's definitely one of the
things we have to think about when using perl on our Mac OS X boxes.
(Urging Peter to add ssh functionality to interarchy might not be on
topic, perhaps.)
--
Joel Rees
Re-inventing the wheel --
One of these days it'll be time to properly implement this wheel thing,
bang off all the corners so it can actually roll.