Re: Why did this copyfile stop working?
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55904
interpreted = N
texte = on 2/3/04 8:32 PM, Kenneth Grome at webdna@kengrome.com so noted... > The waitforfile context does not wait until the new file has been > written completely, it only waits until it 'sees' the new file -- and > it can 'see' the new file before it has been completely written to > disk. > > Therefore, if it is seeing the new file before it has been completely > written to disk, the original file will be deleted prematurely -- > before it has been copied to the new location. Then the OS may be > deleting the partially-written the new file because it could not > finish the copying the 'missing' original. > > If this is the problem, you *should* be able to fix it by writing a > blank file AFTER copying the cart file to the new location. Webdna > will not write the blank file until after the original file has been > copied to the new location. Then your waitforfile context should > wait for the blank file to be written before deleting the original. > This should insure that the original file was copied completely to > the new location before it gets deleted. Yeah, the [waitforfile] was added as a "well, NOW what?" gesture (and sounds like the results would be either none or to make things worse). I'm sure the next thing would have been to wrap [interpret][url] around it. ; ) The waiting for a blank file idea is a good one. Does WebDNA stop processing code when it hits a file operation, or does it initiate the operation and move on? Whichever it is, do the versions on all platforms work the same way? > Movefile has never worked properly from my personal experience. You > seem to have adopted the same work-around technique I've been using > for years. Don't even bother with movefile, it has never been fixed > in all these years so it will probably never be fixed ... It's one thing that didn't need to survive the transition from WebDNA running on Mac OS 9 to running on OS X. Rob Marquardt Designer/Resident Wirehead Toast Design 800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
on 2/3/04 8:32 PM, Kenneth Grome at webdna@kengrome.com so noted... > The waitforfile context does not wait until the new file has been > written completely, it only waits until it 'sees' the new file -- and > it can 'see' the new file before it has been completely written to > disk. > > Therefore, if it is seeing the new file before it has been completely > written to disk, the original file will be deleted prematurely -- > before it has been copied to the new location. Then the OS may be > deleting the partially-written the new file because it could not > finish the copying the 'missing' original. > > If this is the problem, you *should* be able to fix it by writing a > blank file AFTER copying the cart file to the new location. Webdna > will not write the blank file until after the original file has been > copied to the new location. Then your waitforfile context should > wait for the blank file to be written before deleting the original. > This should insure that the original file was copied completely to > the new location before it gets deleted. Yeah, the [waitforfile] was added as a "well, NOW what?" gesture (and sounds like the results would be either none or to make things worse). I'm sure the next thing would have been to wrap [interpret][url] around it. ; ) The waiting for a blank file idea is a good one. Does WebDNA stop processing code when it hits a file operation, or does it initiate the operation and move on? Whichever it is, do the versions on all platforms work the same way? > Movefile has never worked properly from my personal experience. You > seem to have adopted the same work-around technique I've been using > for years. Don't even bother with movefile, it has never been fixed > in all these years so it will probably never be fixed ... It's one thing that didn't need to survive the transition from WebDNA running on Mac OS 9 to running on OS X. Rob Marquardt Designer/Resident Wirehead Toast Design 800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Rob Marquardt
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebCatalog 3.0.4 alias crash bug? (2000)
New WebCatalog Version !!! (1997)
Newbie Help Needed (1998)
1st Comparison inside [fileinfo] broken. = bug? (2004)
supressing math results (1997)
Signal Raised (1997)
Wrapping text (1998)
Using ticks (2000)
Multiple Pulldowns (1997)
Am on the list? (1997)
How long until WebDNA makes the list? :( (2004)
formatting dates from a field ... (1997)
WebDNA Solutions ... (1997)
Cross platform problem with Convertchars (2002)
WebCat hosting providers? (1997)
NT License trade for Mac (2000)
[applescript] (1999)
[WebDNA] Database Error -oRiGiNaL- (2012)
LOOP problem (2007)
Refering page (1998)