We use a series of XCOPYs from a bat file. Inside the bat file, there
are a number of REM statements that get written to an output file, and
the XCOPY writes any error to a logfile. (using the > and >> DOS
redirect commands)
Cold fusion reads these logfiles as they are created, and updates a
webpa
I recommend robocopy. It's part of the windows toolkit or somesuch.
Microsoft makes it. It's quite fast and reliable. A good step up from xcopy.
As for returning when an operation is done, I think that has to do with
not specifying a timeout="" attribute on your cfexecute tag. If you
don't add
Thanks for the advice. The "timeout" thing has me confused, though. What I
really want to do is wait until the process has completed copying. Let's say
that could take as much as 10 minutes (hopefully won't ever be that high, but
not out of the question)--do I really set the timeout to 600?
I stumbled upon this a couple weeks ago, the exact minute I needed it,
believe it or not. This is what I meant by the timeout setting:
http://www.corfield.org/blog/index.cfm?do=blog.entry&entry=C749C0CE-B147-4BBA-F6AF009076498BBA
If it takes longer than the timeout, you can cftry/cfcatch the pro
On 4/13/05, Nathan Strutz <[EMAIL PROTECTED]> wrote:
> Robocopy is especially great because it can copy just the new and
> changed files.
Robocopy is indeed more robust, but Xcopy can do just changed files as
well. /D switch. Requires at least 1 day of difference though.
--
--mattRobertson--
J
Thanks again for the help. I did some experimenting. You can't just check for
the existence of the output file, since Xcopy creates that file right away (so
it can stream output data into it). So, I need to test for the presence of the
file *and* some particular string of text within the file
One of the reasons CF is so slow is its implementation ontop of java.
Java is not wildely fast with system IO, couple this with Coldfusions
implelentation of cffile and you get a slow file IO. We do all of our
file processing with PERL...it is fast really fast. Perl is also
comfortably stable and e
So, you write file manipulation in PERL, then reference those scripts from
using ?
>One of the reasons CF is so slow is its implementation ontop of java.
>Java is not wildely fast with system IO, couple this with Coldfusions
>implelentation of cffile and you get a slow file IO. We do all of our
>
Or you invoke the perl script through http.
Cfhttp works wonderfully for this.
Jerry Johnson
Web Developer
Dolan Media Company
-Original Message-
From: Ben Mueller [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 14, 2005 11:52 AM
To: CF-Talk
Subject: Re: CFFILE slow. Is there a good
9 matches
Mail list logo
