Hi Detlev, Thanks for responding. I too was hoping the problem I'm experiencing was temporary, but I still cannot access many images that are 400px wide or larger. I've noticed that its more widespread that I initially encountered. for instance, I cannot view this image (linked from the picasaweb home page) at....
http://picasaweb.google.com/Aaron.McCullough/MyRecentPhotos#5485985811916518354 Here's a screenshot I just took a few moments ago.. http://dev.cleartours.com/pwaproblem/pwamissingimagechrome20100707.jpg My best guess is that this is a routing issue getting the high res images back to my Comcast IP of 76.16.183.x All computers at my location have the exact same problem. As the hostname is identical for the lowres and highres images, I'm guessing that the high-res images are most likely pulled from a different internal google server. However, on my AT&T wireless phone (currently 166.196.34.x), I can access the high-res images with no problem. I also cannot access some images that are 400px or larger from my test server being hosted over at media temple at 72.47.224.x Very odd and very frustrating.... Any ideas or anyone else seeing this? Lee On Jul 7, 2:43 pm, Detlev Schwabe <[email protected]> wrote: > On Jul 5, 10:39 am, Lee <[email protected]> wrote:> Hi Detlev, > > > Is this a new process that has been recently implemented? I am still > > No, that has been the process for a while (> 1 year at least). > > > experiencing a similar problem as described > > on....http://groups.google.com/group/google-picasa-data-api/browse_thread/t... > > The issue described in that thread sounds like a temporary issue. You > are still seeing this? > > > Also, do you know if this caching process applies when images that > > have been previously uploaded to PWA via Picasa Desktop, and then are > > updated on the desktop, and then updated image is resent to PWA via > > Picasa Desktop? Would the new image be referenced immediately via the > > regular Picasaweb.google.com interface or is there a waiting/ > > processing period until the new image is available? > > The caching process is exactly the same: > A change to the image data will result in different image URLs > (because the version of the image data is part of the URL). The PWA > frontend always uses the image URLs it finds in the most recent photo > entries. That's why changes like those you described will immediately > be picked up. Any 3rd party app that relies on the image URLs directly > can experience a delay up to 24 hours before the old URL will reflect > the new image data. > However, if some other client requests the same image size through the > new image URL, it will also replace the cached data for the old image > URL, thereby resulting in a much shorter refresh delay. Locality plays > a role as well of course with distributed data centers and replication > delays. > > > > > > > Thanks > > > Lee > > > On Jul 2, 9:30 am, Detlev Schwabe <[email protected]> wrote: > > > > When you update the image bytes (including the EXIF data) of an > > > existing photo entry, the version of that photo changes as well as the > > > media:content and media:thumbnail image URLs. > > > However, you will still be accessing the previous photo version for up > > > to 24hrs from our image caches if you continue to use the image URLs > > > from the old photo version. > > > However, if you downloaded your updated photo through the new image > > > URLs, you will receive the modified version, also reflecting your > > > modified EXIF data. > > > After 24 hrs, the old URLs will also point to the updated content. > > > > On Jun 30, 12:15 pm, Ed Lebert <[email protected]> wrote: > > > > > This is very strange. Maybe someone can shed some light on this for > > > > me. Basically exif data on the photo (such as keywords, caption, etc) > > > > isn't updated on picasaweb when you provide an updated file. > > > > > 1. Create a new photo on picasaweb that contains a bunch of exif data. > > > > 2. download the photo and view the exif data using exiftool. > > > > Everything is correct. > > > > 3. change some of the values in the exif data using exiftool. > > > > 4. send your updated file to picasaweb using the API or Picasa desktop > > > > client. > > > > 5. download the photo again and view the exif data. The exif data > > > > wasn't updated! > > > > > I noticed this at first using the normal Picasa client doing the > > > > "update" command on individual photos. But then I starting using the > > > > normal HTTP API manually and witnessed the same behavior. I'd expect > > > > that when I send picasaweb an updated binary file, it then uses that > > > > binary file including it's exif data. That doesn't appear to be > > > > happening. It looks like it strips the image out of the updated jpeg > > > > file and merges it in with the old exif data from the original photo. > > > > > I've even gone so far as to delete the file on picasaweb and then re- > > > > create the new file. After downloading ... still the same old exif > > > > data from the original file which was deleted. This is super strange. -- You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-picasa-data-api?hl=en.
