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.. -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] Behalf Of Chris Velevitch Sent: Thursday, 31 August 2006 2:01 PM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: Why bother On 8/31/06, Joel Cass <[EMAIL PROTECTED]> wrote: > All I am saying is that if you have to go outside of CF to execute a > function, then technically you are not doing things that CF was made to do. I don't understand what you are trying to say. Doesn't CF code get compiled into Java classes which are run on Java based application server of which thread.sleep() is a function with the server? The code generated by the compiler is calling sorts of server functions that you never know or need to know about. The way I see it, there's not real distinction between being in or out of CF, it's all Java. Chris -- Chris Velevitch Manager - Sydney Flash Platform Developers Group m: 0415 469 095 www.flashdev.org.au --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
