Re: [CFCDev] to use or not to use - instance data

[Nathan Dintenfass]

Barry -- if I understand your question, the answer is "no" -- in that 
particular example the idea was to define a caching API that can be 
implemented in any way someone likes.  There were config files where you 
could define which caching implementation to use for a given blog, but 
there was a single code base for all blogs on a server (it acted as a 
"toolkit" that could be used by multiple blogs that each have their own 
custom implementation of that toolkit).

I'm not sure why the two things ("properties" vs. cache interface) are 
mutually exclusive.  I was mostly saying that the onerous interface of 
"server.cfc#id#.method()" could be avoided using something similar to 
the scheme I used in Impart.


Barry L Beattie wrote:
Nathan: did your gateway need to store any values itself (as object properties) or 
just called down into the cache every time?
thanx
barry.b
----------------------------------------------------------
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 www.mail-archive.com/[EMAIL PROTECTED]