Clearly, from a technology standpoint, a meta refresh is a
horse-and-buggy kind of thing, and weak point from many perspectives.
I've actually used the java sleep method before, but I had no idea
that it does NOT tie up a thread.
What about the number of simultaneous processes CF is allowed to run?
If I have CF set to run X simultaneous processes, is the one being
grabbed during an 'execution phase' released during the sleep period
so that process is available for other CF requests?
If so, thats worth doing an MX-specific mail-delivery method. If not,
then the method is effectively tying up a thread.
In one of the Blackstone articles floating around recently, it was
stated that 55% of installations are using CF6+... which means that
45% aren't. A crying shame, but CF5-prior compatibility is a reality
I have to cope with.
--
--Matt Robertson--
MSB Designs, Inc.
mysecretbase.com
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
[Donations and Support]
- Re: cfmail Simon Whittaker
- CFFILE READ one line at a time Terry Troxel
- RE: CFFILE READ one line at a time Paul Vernon
- Re: CFFILE READ one line at a time Dick Applebaum
- Re: CFFILE READ one line at a time Novak Banda
- Re: CFFILE READ one line at a time Michael Dinowitz
- RE: CFMail Ryan Duckworth
- RE: CFMail Trevor Holm-Laursen
- Re: CFMail Matt Robertson
- RE: CFMail Ryan Duckworth
- cfmail Matt Robertson
- cfmail Tangorre, Michael
- Re: cfmail Jochem van Dieten
- RE: cfmail Andrew Dixon
- RE: cfmail Ray Champagne
- RE: cfmail Tangorre, Michael
- RE: cfmail Tangorre, Michael
- Re: cfmail joe velez