I've never thought of doing that. I would probably first consider throwing
more hardware at the issue, after optimizing of course. But now that you
brought it up, it seems like it could be useful in a couple of situations.
Perhaps to display more or less search results per page based on load (i.e.
Results_Per_Page = 100 * 10 / Num_Of_Concurrent_Users). Or to display
non-critical bonus features when load is low. Something to think about...

I don't know of any CF8-specific features that would do this, but I could
imagine a way:

   - LoadManager.cfc keeps track of total load (num.of sessions,
num.ofhits, etc.)
   - Factory.cfc references LoadManager.cfc and uses it to verify total
   load before running createObject()

Perhaps an AOP option too.

Baz


On 10/30/07, Mark Mandel <[EMAIL PROTECTED]> wrote:
>
>
> Maybe for algorithm style work, where you are sacrficing speed for
> memory, and vice versa.
>
> Maybe?
>
> Mark
>
> On 10/31/07, Derek P. <[EMAIL PROTECTED]> wrote:
> >
> > Just curious, why would you ever want to build something that purposely
> (and
> > most likely needlessly) ate resources if you had a leaner solution to
> doing
> > something?
> >
> > - D
> >
> >
> >
> > On Oct 30, 2007, at 7:24 PM, Mark Ireland wrote:
> >
> > Anyone done components like this:
> >
> > If loadHigh
> >
> >   invoke simple (resourceLean) components
> >
> > ElseIf loadLow
> >
> >   invoke fancy (resourceHog) components
> >
> > (Are there CF8 features that make this easier?)
> >
> > ________________________________
> > Listen now! New music from the Rogue Traders.
> >
> >
> >
> >
> >  >
> >
>
>
> --
> E: [EMAIL PROTECTED]
> W: www.compoundtheory.com
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to