> > GaeVFS is built on top of the Google datastore
Ah I thought it was a RAM based file-system. Just for my own edification, if cffile goes directly into the datastore, why the GaeVFS intermediete layer rather than just have cffile use JPA behind the scenes - or even implement your GoogleWrite() with the key filled out automatically as a path? Baz On Wed, Jun 17, 2009 at 1:22 PM, Vince Bonfanti <[email protected]> wrote: > GaeVFS is the underlying virtual file system that I created to implement > CFDIRECTORY, CFFILE, CFCONTENT, and other file-system based operations that > need a writable file system. GaeVFS is built on top of the Google datastore; > therefore, your first and third bullet points are the same thing (if you're > writing CFML code you don't need to write directly to the datastore as text > or blob, just use the CFFILE tag). I decided to release GaeVFS as a separate > project because it may have some general applicability beyond OpenBD. > > Some other interesting use-cases: just about anything for which you're need > a writable file system. For example, both the CFCHART and CFSEARCH tags in > BD need to be able to write temporary files--I plan to use GaeVFS for these > implementations. > > Currently, GaeVFS is limited by the 1MB entity limit of the Google > datastore. I have plans to implement an "entity-chaining" mechanism that > will remove this limitation (files bigger than 1MB will be stored across > multiple entities). Before writing this code, I'm waiting to see what Google > is doing for "big file support" that's on their roadmap. > > Vince > On Wed, Jun 17, 2009 at 2:52 PM, Baz <[email protected]> wrote: > >> Vince I didn't know you invented the >> GAE-VFS<http://www.mail-archive.com/[email protected]/msg10479.html>, >> very cool! >> >> So there are 3 places to store files: >> >> - In the Datastore as Text or Blob >> - Dynamic, usable at run-time, mainly for end-user >> uploads/downloads >> - 1mb limit per file >> >> - Compiled into your project >> - Static, mainly for site assets like images or flash movies >> - 1,000 file limit, but that must include all cfm's, jars, libs, >> javascript and other code, etc. >> >> - GAE-VFS >> - Dynamic, non-permanent >> - Not sure what the limits are >> >> So is the GAE-VFS mainly for easier migration of cfml applications? Are >> there other interesting use-cases to consider? Maybe for example as an >> intermediete layer to store big files in S3? Or perhaps one could have users >> upload files slightly larger than 1mb to the VFS, then have the app >> compress/zip them to below 1mb for storage in the Datastore (is that even >> possible)? >> >> Does google have a plan or answer for files bigger than 1mb, or are we >> expected to use another service like S3 for that purpose, and store the >> links/metadata of those files in the Datastore? >> >> Just to be sure, if you had a site with lots of file upload and download >> activity of files under 1mb, the Datastore is tuned and built for such >> in/out activity, correct? >> >> Cheers, >> Baz > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
