Just for clarification: There seems, to me, to be a big distinction between "support for large files" (to me, that sounds like serving bigger files that I upload via appcfg) and supporting large files uploaded by end-users (which, to me, implies letting the web app store data in bigger BLOBs).
It seems perfectly workable (if a nasty bit of coding) to treat the database BLOBs as a virtual file system, breaking a file into multiple chunks and streaming them back one at a time. But actually uploading such a thing means getting over the 1 MB request limit. Is that part of the plan? Thanks yet again, James On Dec 17, 11:47 am, Marzia Niccolai <[email protected]> wrote: > Hi Brian, > > These two features (billing and large file uploads) are being worked on > concurrently but their release dates are not tied together. They both are > on the roadmap for Q1, and are still on track for that time. We haven't yet > determined the maximum size for large files. > > -Marzia > > On Wed, Dec 17, 2008 at 4:40 AM, BrianJinwright <[email protected]> wrote: > > > I agree it is possible in s3 just set the ACL of that bucket or > > object. I think yu Ping's question is a good one. When billing is > > opened up will can we store files larger than 1MB. If so, how large. > > > Thanks, > > Brian Jinwright > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
