>Maybe. Have you looked at it? Can you give me a summary of how they've >implemented it?
Not in a while. But I believe its close to your #2 choice. It would make sense to first check for the existence of the virtual file system mapping before checking the disk though. Regarding the large file support, it seems to me that a virtual file system for OpenBD GAE could be done for the datastore AND any future implementations of data storage. So if you've done enough to move ahead on this first implemenation you may want to go ahead and finish it and add a way of extending this for future iterations of the appengine api for data storage. On a seperate matter how difficult would it be to include support for java/groovy classes for the Google Datastore methods googlewrite() googlequery() etc...? I'm guessing you're serializing cfc components for these functions. As they works now however, if you use any sort of DI on an entity cfc, or use a java entity the datastore methods fail - which makes them less useful. --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
