[google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-16 Thread Stuart Langley
What's the image URL? On Sunday, 16 September 2012 14:40:35 UTC+2, Tim wrote: > > Hi, > I've just migrated one of our App Engine applications from Blobstore to > Google Cloud Storage and am using the ImagesService.getServingUrl to serve > images. > After uploading a new/changed image using a Goo

[google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-17 Thread Tim
The image url is: https://lh3.ggpht.com/gpsljr0tsbBZM8g1GhV3KnTe4I5veZpIux0jJGSqbpJA_pSEWACtHpNbguEoqWpzTuTDTae1LgG05AAeZybBog The GCS name is: gs://86010.mypanel.eu/projects/372001.jpg I currently use the ID of the datastore object for the GCS name, everytime I upload a new image using this sam

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-17 Thread Nickolas Daskalou
I can confirm we also have (or at least had) this issue. In the end we bit the bullet and created timestamped copies of any file we updated in Google Cloud Storage, then used the serving URL of the timestamped version. If I can find the URLs I'll send them through. Nick On 17 September 2012 18

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Stuart Langley
OK I just heard back from the team that runs this service. 1. If you change the file in Google Storage without changing the filename, then you'll need to do a deleteServingURl/createServingURL for the file. Essentially when you createServingURL there is some work done to prepare your images fo

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Stuart Langley
One more thing - Google storage is going to implement notifications when objects change, so we might be able to do step (1) automagically. Probably a feature request for that might be a good idea if you think it would be useful. On Tuesday, 18 September 2012 08:20:53 UTC-7, Stuart Langley wro

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Tim
Thanks Stuart, our users upload (possibly changed) images through a web form and we want the (possibly changed) image to appear immediately after uploading (instead of a maximum of 24h) to prevent confusion. So for now I will make sure the images have unique names everytime they're changed. I f

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Stuart Langley
Just use the API to create a blobkey from a Cloud Storage filename and delete will work fine. It should be possible to use a blobkey that points to a Cloud Storage file in any API that accepts a blobkey - e.g. serve(), images etc. On Tuesday, 18 September 2012 09:08:51 UTC-7, Tim Rob wrote: > >

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Tim Rob
Thanks, I will keep that in mind. On Tuesday, September 18, 2012 8:30:56 PM UTC+2, Stuart Langley wrote: > > Just use the API to create a blobkey from a Cloud Storage filename and > delete will work fine. > > It should be possible to use a blobkey that points to a Cloud Storage file > in any API

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-18 Thread Nickolas Daskalou
Thanks for looking into this Stuart. When you say "we might be able to do step (1) automagically", do you mean the GAE team will do this for us, or us app developers will need to do it? If it's the former, do we still need to submit a feature request? Nick On 19 September 2012 01:24, Stuart Lan

Re: [google-appengine] Re: ImagesService.getServingUrl returning old image with Google Cloud Storage

2012-09-19 Thread Stuart Langley
-> submit feature request On Tuesday, 18 September 2012 20:59:17 UTC-7, Nickolas Daskalou wrote: > > Thanks for looking into this Stuart. > > When you say "we might be able to do step (1) automagically", do you mean > the GAE team will do this for us, or us app developers will need to do it? > I