You could also try cfexecute with a call to cfml.exe calling a page that
calls cfhttp. I don't think this would cause errors in the log files, but
it would probably use up a few more threads.
Just add abstraction layer upon abstraction layer :)
Spike
At 10:02 23/05/2001 Wednesday, you wrote:
> > 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.
>
>Right. I was also wondering what the timeout will do to the general sanity
>of the CF process. For example, every cfhttp-to-itself-with-1-sec-timeout
>will generate an error 232 in the server.log.
>
>Also IIRC scheduled tasks take up two threads, so if the server is fully
>loaded might these not generate problems as well?
>
>What would be cool is some kind of background daemon that sends HTTP
>requests and just eats the results and can interface with CF via CFX or
>something. (Hm I might even have a go at this myself. :)
>
>--
>Michiel Boland <[EMAIL PROTECTED]>
>Digital Valley Internet Professionals
>Plantsoen 17, Wageningen, The Netherlands
>Phone: +31 317 465555, Fax: +31 317 460276
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
