that one ;-))
Taco Fleur
Blog <http://www.tacofleur.com/index/blog/>
http://www.tacofleur.com/index/blog/
Methodology http://www.tacofleur.com/index/methodology/
0421 851 786
Tell me and I will forget
Show me and I will remember
Teach me and I will learn
-----Original Message-----
From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 3:11 PM
To: CF-Talk
Subject: RE: CF Start a process - don't wait for it to finish
gotcha... in this case I'd recommend a similar solution. Use cfhttp to
execute the other page and then use cflocation to redirect to
someplace else. I _think_ you can execute cfhttp with a timeout of 0
and have the page continue processing immediately without waiting for
the cfhttp content. I'm not certain of this tho -- I don't do a lot of
work with cfhttp, so I'd have to go back to the docs and test it. For
my own work, I have yet to run into any real issues with the way the
framework handles it -- doesn't mean there aren't any, just that I
haven't experienced them. Of course the framework also encapsulates
the processes executing in the onrequestend to insulate them some from
the remaining page.
> That sounds like it would do the trick - but like you said
> there are some
> concerns, it might be a last resort.
> But preferably I'd like it so that once the other process
> is called it has
> nothing to do with the originating page, I know its asking
> a lot;-))
> Taco Fleur
> Blog <http://www.tacofleur.com/index/blog/>
> http://www.tacofleur.com/index/blog/
> Methodology http://www.tacofleur.com/index/methodology/
> 0421 851 786
> Tell me and I will forget
> Show me and I will remember
> Teach me and I will learn
> -----Original Message-----
> From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 22 January 2004 2:33 PM
> To: CF-Talk
> Subject: Re: CF Start a process - don't wait for it to
> finish
> The onTap framework has a built-in method of doing this
> which is
> easily portable to other applications. Basically you
> generated content
> then use cfflush to push that content to the user, and
> perform the
> NSLookup (however it's performed) after the flush, so it
> processes
> after the user has already received their content. The
> onTap framework
> does this by providing a default flush and a queue of
> processes to be
> executed in the OnRequestEnd.cfm template. If you have
> concerns about
> users refreshing the page and causing unnecessary overhead
> on the
> system, you might want to include a page redirection (meta
> tag or
> _javascript_ - you can't use cflocation after a cfflush tag)
> in the
> content going to the browser. I use the _javascript_
> location.replace()
> method which is analogous to cflocation in that it
> replaces the
> current entry in the browser's history, allowing the user
> to use their
> back button normally. The onTap framework has this
> function
> encapsulated into a couple of ColdFusion functions which
> provide some
> additional features.
> hth
> s. isaac dealey 214-823-9345
> team macromedia volunteer
> http://www.macromedia.com/go/team
> chief architect, tapestry cms http://products.turnkey.to
> onTap is open source http://www.turnkey.to/ontap
>> What's the best way to start/call a process in CF and not
>> wait for it to
>> finish?
>> I'm thinking cfhttp but not sure...
>> For example:
>> A page is called, this page does a NSLOOKUP etc. which
>> takes a bit of time,
>> but I don;t want to user to have to wait for the process
>> to finish, i.e.
>> prevent unnecessary delay of the page loading time.
>> Taco Fleur
>> Blog <http://www.tacofleur.com/index/blog/>
>> http://www.tacofleur.com/index/blog/
>> Methodology http://www.tacofleur.com/index/methodology/
>> 0421 851 786
>> Tell me and I will forget
>> Show me and I will remember
>> Teach me and I will learn
>>
> _____
>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
