"This whole thing about trying to replace an object with some cached 
version is the unnecessary complexity. If your plantSet is meant to be 
a Web Service, it should be stateless - have no instance data - and 
simply manage the cached data (in server scope, for example). No "this" 
scope stuff, no "variables" / unnamed scope stuff - stateless CFCs 
don't need that."

Just a as a follow-up to make sure I understand. If I have a bunch of
service-type methods in either the application or server scope, how do I
ensure that any services they perform (such as data retrieval) don't keep a
lot of unwanted data hanging around when it won't be used again?


Walt

----------------------------------------------------------
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).

Reply via email to