Firstly, thanks as always for the response. > If you mean physical files that are in the WAR directory and deployed as > part of the application then yes, they're read only. You cannot write to the > local file system on GAE, hence the VFS.
This may be a dumb question but "where" is the VFS? By this I mean the WAR directory is uploaded to GAE. To me this would infer every file in the WAR canNOT be written to (changed) by say a web visit. I'm still so noob I don't know if you would ever want such web based modification nor if this is even relevant but if not then I assume the port to GAE puts OBD code into a VFS so that CF can write internals?? > Short answer is CFIMAGE hasn't been > ported over to GAE yet. Google does have an image manipulation service > available as part of the GAE offering though, which Peter and I demoed in > our CFMeetup talk. I'll make that code available this week. Awesome. > Yes and no--bluedragon.xml doesn't deal with the settings you would normally > handle via Application.cfc or the CFAPPLICATION tag. Think of bluedragon.xml > as all the stuff you'd do via the admin console. Adding an Application.cfm file and OnRequestEnd.cfm(note it turns out OnRequestEnd.cfm does not run if there is not also an Application.cfm) works "as normal" . . . do you by any chance have a recommended or illustratory (commented) Application.cfc file which you could post? I know I had one for CF that I will find (and post here) shortly either way. -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
