So how should we handle filename/path conflicts when writing files? Consider this (assume a filename of "mypicture.jpg"):
<cffile action="upload" destination="/images" nameconflict="overwrite" /> What happens if I find "/images/mypicture.jpg" on the real file system? The CFML coder has said he wants to overwrite the existing file, but I can't because GAE won't let me delete the file. If write "/ images/mypicture.jpg" to the virtual file system, then the CFML coder can never read it because CFFILE ACTION="READ" says, "check the real file system first, then the virtual file system." Do we reverse that and say, "check the virtual file system first, then the real file system"? What problems or confusion does this cause? Do we throw an exception? My point is: making things transparent is complicated to implement, and may lead to confusing and unexpected behavior. Making things explicit is easier to implement, makes the CFML programmers intentions clear, and avoids confusion. On May 13, 11:22 am, Adam Haskell <[email protected]> wrote: > > Doh...that should read #1. > > > > On Wed, May 13, 2009 at 11:21 AM, Adam Haskell <[email protected]> wrote: > > # all the way, maybe an additional method would be in order > > FileAccesMethod(myFile) would return the access method used. This could be > > expanded as well like Railo uses in memory files as well, it might be worth > > while exploring what Railo is doing in that space. > > > Adam- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
