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

At 10:14 PM 5/22/01 +0200, you wrote:
>One of my co-developers came up with an interesting idea. There are some
>things that can take a while to process, like metadata updates, workflow
>updates, etc. These things combined take a few seconds to run. Now, to
>increase the page speed from a user's point of view these things can be
>run 'in the background' using the following hack.
>
>The .cfm that is executing performs a CFHTTP to another template on the
>same server that does all the time-consuming bits. The CFHTTP has a
>timeout of one second (I tried CFHTTP with timeout=0, that did not appear
>to have the desired effect. :)
>
>This should work, but I have some moral reservations. :) Has anyone else
>toyed with this sort of thing?
>
>Cheers
>Michiel
>
>--
>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.

Reply via email to