On Sep 1, 2010, at 2:31 PM, Barry Hunter wrote:
Have you considered using the Storage API?
http://code.google.com/apis/storage/
No I haven't seen it. It looks very promising -- thanks for the tip! I
signed up and I hope I can get access in time. It makes me think the
blobstore isn't much use.
rather than the blobstore.
S3 I believe imposes a 5Gb limit per file. The storage API has a limit
of 100Gb - but that is mentioned as a limit during hte preview, so
might be raised.
Yes, that's true, but 5G doesn't reek of of design flaw the way 2 and
4 does, so there's a reasonable hope that it will go up.
bjorn
On 1 September 2010 14:15, bejayoharen <[email protected]> wrote:
Sorry if I missed this somewhere, but I am considering building an
app
using GAE for a big new project. I've been reading everything through
carefully and it seems very cool and exciting. Most of the
limitations
people are complaining about don't frighten me in the least. However,
a few things struck me about the blobstore:
1. the API is a bit awkward. I am looking around for sample code,
preferably a REST-style API, rather than something a browser would
use. WebDAV is in this spirit, so I checked out the code for gae-
webdav, but it does not seem to use the blobstore, so its file sizes
are limited to whatever the Datastore is limited to (10 MB right now,
I believe). I don't have direct experience with S3, but I know people
do this with S3.
2. The blobstore file sizes are limited to 2GB. Is this DOS? are we
in
the mid 1990s? I realize most users today aren't using the web for
files greater than 2GB, but, well, 2GB is a suspiciously non-
arbitrary
sounding number.... and it's an app-killer for me. the 2 GB file-size
limit (and it's close cousin, the 4GB file size limit) used to be one
of the most frustrating aspects of serious multimedia apps to many
users before modern file systems came along, and to see it rear its
ugly head on the the web... well... I'm concerned. Is this something
we can request to have expanded or that will be expanded in the
future, or are we stuck with this? The vast majority of files I plan
to deal with will be small, just a few megs, maybe a few hundred
megs,
but customers will want to move huge files, and I want to assure them
it will not be a problem.
So, what are my options? Is it possible to extend this limit? has
anyone developed a rest/dav-like interface? should I opt for S3?
Sorry if I am missing something, but the ability to transfer what I
consider large files via a programmer-friendly (preferably Rest) API
is not optional and I want to square this away before committing to a
platform, so if anyone has pointers as to how I can do this, I'd
appreciate it.
thanks
bjorn
--
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
.
--
You received this message because you are subscribed to the Google
Groups "Google App Engine" group.
To post to this group, send email to google-
[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
.
-----------------------------
Bjorn Roche
XO Audio, LLC
Audio Software & Digital Audio Consulting
http://www.xoaudio.com
http://blog.bjornroche.com
--
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.
