Hi Stephen,
I couldn't see the promotion being applied after enabling billing. Anyway,
let's see if release 1.7.0 is any different, they say you can set header
for static contents now (maybe you can set the encoding type now).
As far as I understand static content/blobs are the same for the purp
I signed up for a GCS account relatively recently, and I certainly got the
free quota (https://developers.google.com/storage/docs/pricingandterms)
applied. It's easy to miss though - to see whether it's active you need to
go to the API Console and choose the 'Billing' option from the menu. When
Thanks for that, I tried to setup Cloud Storage and thought that I could be
on a free quota (we're already paying for GAE and didn't really want to pay
again for something that GAE should be doing). Anyway, if there's a free
quota for Cloud storage, I don't know how to enable it.
The cost of wor
Stuart,
The issue "2820" has been hanging fire for quite some time now (30 months).
It would be a huge help if we could get visibility into whether it would
ever be addressed.
http://code.google.com/p/googleappengine/issues/detail?id=2820
Thanks,
Sameer
On Thu, Jun 21, 2012 at 5:07 PM, Stuart L
Curiosity got the better of me, and I've just tried this - unfortunately,
it doesn't work. When serving from Google Storage using send_blob I
received the pre-gzipped content, but the Content-Encoding header was not
sent.
You might want to try something with signed URLs (
https://developers.goo
Thanks for the tip! I will certainly try next week. Storing two versions
would be nice and easy to do!
On Friday, 22 June 2012 23:38:40 UTC+12, Stephen Lewis wrote:
>
> When you serve up a Cloud Storage object directly from Cloud Storage, you
> can certainly pre-gzip the content and make sure it
When you serve up a Cloud Storage object directly from Cloud Storage, you
can certainly pre-gzip the content and make sure it's served with the
correct 'Content-Encoding'. The reference to this is at:
https://developers.google.com/storage/docs/reference-headers#contentencoding
I'd be interested
On Friday, 22 June 2012 18:35:49 UTC+12, Brandon Wirtz wrote:
>
> Cloud flare would still suck the uncompressed file down and then zip it,
> that is unlikely to speed things up.
>
> Check my old posts about headers for edge cache, my guess is that you have
> the expiration set in the past or im
thanks for the suggestion. The resources I was talking about are large but
not static, that's I've been using compressed entities and now the blob
store.
Have given up on the blob store for now, and reverted to compressed
entities.
Might try with the Google cloud store.
On Friday, 22 June 2012
.
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Richard Watson
Sent: Thursday, June 21, 2012 11:09 PM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Re: Large text files from blobstore are not
being gzipped (AppEngine Java)
As
As Jeff mentioned on the SDK thread, maybe try Cloudflare.com. I've just
turned it on and it's not too painful, although I had to set up my page
rules just right. If you have static content, they'll gzip and cache it
for you on their CDN.
One option if you don't want them proxying your whole
Thanks Stuart,
indeed it looks like the same issue. I'm gonna try loading the blob content
in memory first.
It's going to be slower but that's what I've been doing until yesterday: I
was compressing large entities and storing them in up to 1MB sized
entities. I switched to the blobstore in orde
Probably http://code.google.com/p/googleappengine/issues/detail?id=2820
On Thursday, 21 June 2012 19:56:20 UTC+10, Emanuele Ziglioli wrote:
>
> Hi everyone,
>
> I'm serving a number of text files from the blobstore and while smaller
> ones are being gzipped by the frontend servers, larger ones ar
13 matches
Mail list logo
