[google-appengine] Re: Images API still limited to 1MB

2009-04-27 Thread Emilien Klein
As I'm currently developing a site that allows users to upload photos (which would typically be taken with a digital camera), I am sure to hit that 1Mb limit on the images API calls. I would love to have the possibility to resize those images directly in App Engine, however as stated before in

[google-appengine] Re: Images API still limited to 1MB

2009-04-27 Thread Emilien Klein
I'm currently developing a website that will require users to upload a few photos of their houses. There is a pretty good chance that those photos will be taken with a digital camera, and thus bigger than 1Mb. In order to save space, I would like to resize them to more web- friendly dimensions,

[google-appengine] Re: Images API still limited to 1MB

2009-04-20 Thread Tim Hoffman
Hi I suppose you need to remember app engine is a horizontally scalable application framework and not a cpu intensive cluster. Whilst google's infrastructure might seem massive I imigine it is not infinately scalable. So limiting image sizes - thus limiting the potential intensive ness of

[google-appengine] Re: Images API still limited to 1MB

2009-04-19 Thread Andy Freeman
For a processing API call like an image API call, there should be no dependence on BigTable or any sort of clustering It has been said that the image API is actually executed on an image processing cluster, not the application servers.

[google-appengine] Re: Images API still limited to 1MB

2009-04-18 Thread Tim Hoffman
Why don't you stick the images in Picasa and just manage them through app engine ? Thats what I am doing T On Apr 18, 4:28 pm, Anuraag Agrawal anura...@gmail.com wrote: When App Engine raised its request size limit from 1MB to 10MB, it seemed like we would finally be able to use it for an

[google-appengine] Re: Images API still limited to 1MB

2009-04-18 Thread Anuraag Agrawal
Indeed the entire API is limited to 1MB, but the point of discussion I'd like to make is that for data-related API calls like the datastore and memcache, it's easy to come up with hardware/implementation constraints that would warrant such a limit, and there are usually relatively simple ways to