Barry Beattie wrote:
so no one has used XML files as a data source within DAO's ?Although, I haven't worked if xml files with CFCs much...I don't see why you can't wrap a named lock around the required methods...as Roland stated, you'll have to interact with the file system as some point or another. I'd rather let the CFC control locking than the calling code - then if you want to change something, you only have to change the CFC and not tons of line of calling code. Secondly, since it looks like you want/need to lock access during operations - if you forget to lock something in the calling code, you might end up with some strange and random results when the application is under stress.
I just need to confirm that locking for file access (read, write, delete) is kosher within a cfc and that there's nothing I've missed...
cheers
barry.b
If you are worried about locks piling up, you might consider having a dynamically named lock based on a hash of the directory and file name. Using a hash will eliminate any possibility of accesing files that share the same name, but are located in different directories.
Best, .Peter
-- Peter J. Farrell :: Maestro Publishing
blog :: http://blog.maestropublishing.com email :: [EMAIL PROTECTED]
Create boilerplate beans! Check out the Mach-II Bean Creator - free download. http://blog.maestropublishing.com/mach-ii_beaner.htm
Windows 95: Most expensive OS/2 backup disks I've ever purchased. --
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
