I think it makes sense to have a single CFC that encapsulates access to the file system so that rather than having <CFFILE>s and <CFDIRECTORY>s throughout the code all file system related operations go through the CFC. To date, I've only seen that concept in practice once so I wouldn't call it a "pattern." (But I haven't seen many CFCs. It wouldn't surprise me is someone else has seen it dozens of times and has a specific pattern name for it.)
The purpose of a DAO is to persist data in such a way that the peristence mechanism is hidden from the client that uses the data. That persistence mechanism may be an RDBMS, an LDAP directory, an XML file, a flat file, a set of directories and files, etc. I hope that makes sense. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.blogspot.com I still have 5 gmail invites. ---------------------------------------------------------- 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]
