Thanks Nick!
On Wed, Jul 22, 2009 at 3:56 AM, Nick Johnson
(Google)nick.john...@google.com wrote:
Hi Jeff,
When I said 10MB, I was referring to the 10MB request size limit, and
pointing out that the forthcoming blob API will allow storing blobs
larger than that size also. You can currently
Hi Jeff,
When I said 10MB, I was referring to the 10MB request size limit, and
pointing out that the forthcoming blob API will allow storing blobs
larger than that size also. You can currently store anything up to
10MB by splitting the blob into multiple datastore entities, but it's
impossible
Yeah, just trying to get clarification. Nick's email stated 10MB,
Wikipedia says 1MB with a 10MB response limit. If Wikipedia is right
and I can get 10MB in/out the door, I can always fragment (or wait, or
if Nick says it is now 10MB ... :-).
3) Along those lines, has anyone implemented something like multi-blob
fragmentation/reassembly for storing serving things greater than
1MB?
I have implemented a basic app for this.
http://simpleupdown.appspot.com/ allows file upload until 10MB.
You can check codes here:
3) Along those lines, has anyone implemented something like multi-blob
fragmentation/reassembly for storing serving things greater than
1MB?
I have implemented a basic app.
You can check from: http://simpleupdown.appspot.com/
and the codes are here:
On Jul 18, 8:29 pm, Jeff Enderwick jeff.enderw...@gmail.com wrote:
Is 10MB the current limit, or is it 1MB? I was under the impression
that the max blob size was 1MB, and max HTTP response size was 10MB.
Do I have it right?
API calls are limited to 1MB unless that's been changed without an
Is 10MB the current limit, or is it 1MB? I was under the impression
that the max blob size was 1MB, and max HTTP response size was 10MB.
Do I have it right?
On Thu, Jul 16, 2009 at 2:15 AM, Nick Johnson
(Google)nick.john...@google.com wrote:
Hi Jeff,
On Thu, Jul 16, 2009 at 3:33 AM, Jeff
Hi Jeff,
On Thu, Jul 16, 2009 at 3:33 AM, Jeff Enderwickjeff.enderw...@gmail.com wrote:
1) I saw that 30 was listed somewhere as the max simultaneous dynamic
requests for an app. Is this really true? Even if I am paying, and I
have a very popular app? I see the math indicating that one can
I'm pretty sure #1 is correct. Of course, it's not a hard limit in
the sense that the 31st request is dropped, rather it's queued, but
yes it's unfortunate.
On Jul 15, 10:33 pm, Jeff Enderwick jeff.enderw...@gmail.com wrote:
1) I saw that 30 was listed somewhere as the max simultaneous dynamic
