On Jan 25, 6:22 am, James Ashley wrote:
> On Jan 9, 3:34 pm, niklasr wrote:
>
> > example: upload a 2 MB file through a html form, split it serverside
> > into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
> > It's inconvenient yet a method to serve large files with no differen
On Jan 9, 3:34 pm, niklasr wrote:
> example: upload a 2 MB file through a html form, split it serverside
> into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
> It's inconvenient yet a method to serve large files with no difference
> towards the client.
Is this a new development
I don't mean when the user uploads files. I mean when I do (i.e.
through appcfg.py). Does it hurt performance if GAE has like 700
static files from me...?
On Jan 9, 4:34 pm, niklasr wrote:
> example: upload a 2 MB file through a html form, split it serverside
> into 2 or 3 parts, then store the
example: upload a 2 MB file through a html form, split it serverside
into 2 or 3 parts, then store the parts as blobs of max 1 MB each.
It's inconvenient yet a method to serve large files with no difference
towards the client.
On Jan 9, 8:36 pm, MajorProgamming wrote:
> I'm not sure I understand
I'm not sure I understand you. Which question # were you trying to
answer?
On Jan 9, 3:26 am, niklasr wrote:
> Reversibly breaking and remaking larger than 1MB files persistently
> storing max 1 MB chunks, gae http get and post support the larger. The
> gae http transport as it is handles larger
Reversibly breaking and remaking larger than 1MB files persistently
storing max 1 MB chunks, gae http get and post support the larger. The
gae http transport as it is handles larger files. The 1MB limit only
limits the entities, not the transport.
On Jan 8, 11:59 pm, MajorProgamming wrote:
> Jus
