> Cool! That's the way most patterns start - they're not really cooked > up, they're just things developers started doing, then said to each > other "Hey! I do that too! Let's call it something so that we can > share the technique."
That makes sense. I've read about and sat through presentations on design patterns. I'm just a no-nonsense kind of guy. I like to call the kettle black, instead of "Having an absence of light". ;) > It _can_ add some upfront time, but it's been my experience that when > stuff starts changing (and we know it's going to!), having "everything > in its place" can be a lifesaver. And has anyone ever considered the overhead CFCs add to your app's processing time/RAM usage? I know that is a fact, but it all depends on how the CFC is built, how often CFCs are used, how large your app is, bandwidth, etc. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
