Hey Joel, While usually you want to get the response back asap, there really are good reasons for a server to put a thread to sleep in some situations - sometimes you need to delay a thread between retries, and you'd like to yield to other threads while you wait - the only alternative would be a busy loop which would burn up CPU watts for no reason and deny use of the CPU to other threads. Often the thread is a utility/asynchronous request not involved in sending a response to the browser, it's a simple way to use a CF thread as a daemon process, keeping the one request going instead of multiple requests triggered by the scheduler.
Cheers, Robin On 31/08/2006, at 2:22 PM, Joel Cass wrote: > > I'm talking more about what CF was *designed* to do. Adobe would have > realised that releasing a CFSLEEP tag might cause some users to > complain > about the server hanging all the time when really it's the > excessive use of > the tag which is the problem.. So they never released this > "function" within > "CF".. > > I'm just taking the fundamentalist view on all this.. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
