I'd say that in a well-designed OO-style system, your components will either be stateless (service-like) and can be cached in application / server scope or they will be small, lightweight and fairly fast to create.I find that interesting, you seem to be implying that 'stateful' objects are a bad thing. Could you explain or point me at some articles ?
No, I'm just saying that I would aim for:
- stateless service-like components (that can be "heavy" and slow to create)
- stateful components that are small and light
In other words, avoid big complex stateful components if possible. I use a lot of stateful components but they (generally) don't have a lot of methods and they don't do much during 'construction'.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
