I'm not a beaniac yet, I'm just toying with the idea while I have some free time. ;)
Let's say you need to store session-based information about a user. This is to make it easily-accessible for any subsequent page requests. Right now, I use a CFC that holds the data and a lot of other stuff that probably shouldn't be there. How do you handle a similar situation? Do you, at least, use a session-based struct? M!ke -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roland Collins Sent: Wednesday, November 17, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] Validation Uh-oh - I hope I haven't made you into a bean maniac :) That was actually one of the _few_ places I would ever use a bean! Beans/DTOs are great for moving data between platforms and systems, but that's the only place I use them. When I'm working in CF, my methods are "parameters in, queries out". This saves the overhead of serializing and de-serializing beans on every call, which can potentially be a large bottleneck. Roland ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at [EMAIL PROTECTED]
