get_serving_url() Pros: - serves from a high-performance CDN (presumably) - allows me to specify sizes dynamically "=s180", generating and caching the resulting image - offloads b/w costs away from my GAE app (probably an overall minimal gain) Cons: - serves off-domain and does not participate in PageSpeed optimizations
PageSpeed Service Pros: - does a bunch of on-the-fly image optimizations automatically Cons: - requires me to serve an image on-domain, so I need to read and serve the image from Cloud Storage via blobstore API - since I'm serving the blob myself, I can't dynamically specify a size - or at least I need to build up the bits to generate and cache the re-sized image on my own - uncheap (though not my primary concern) Am I understanding this correctly? Does anyone know of a way to get the best of both worlds? Specifically, I want to be able to store raw images in Cloud Storage, and then serve them out with dynamic sizings, but also have PageSpeed work its magic on the served image. Possible? Maybe someday? Thanks for any info, j -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
