I've done this sort of thing on a Spectra project. I'd say it's a bit more
efficient than cfschedule - basically cut to the chase and just hit the url
instead of creating scheduled task first. The timeout=1 is very important,
without this you can lock up all your processing threads if the server is
under load. We also used cfhttp for intra-server communication, e.g. an
object changed on the content staging server, use cfhttp to invoke a utility
script on the live server that takes oid as url parameter, clears html
caches related to that object, updates collections etc. You can also do
some amazingly large file transfers between servers using cfhttpparam.
Cheers,
Robin Hilliard
Senior Product Support Engineer - Asia Pacific
Macromedia, Inc.-----Original Message-----
From: Jim Biancolo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 23 May 2001 7:39 AM
To: Spectra-Talk
Subject: Re: Background processing
Interesting . . . I don't have first-hand experience with either approach,
so I'll ask: does this approach offer any advantages over creating a
run-once event to execute in the very near future via CFSCHEDULE?
Jim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
